Detecting and using mood-condition affinities

ABSTRACT

Concepts and technologies are disclosed herein for detecting and using mood-condition affinities. A processor that executes an affinity service or affinity application can obtain collected data associated with a user device. The collected data can include sensor readings collected by the user device. The processor can determine a condition at the user device and a mood associated with the condition. The processor can generate an affinity that defines a relationship between the condition and the mood and store the affinity at a data storage device.

BACKGROUND

Over the past several years, there has been a huge growth in the use ofportable computing devices such as smartphones. Most modern consumersuse portable computing devices such as smartphones not only forcommunication, but also for emailing, web browsing, social networkingapplications, taking photographs and videos, health applications,business applications, and other purposes. With the proliferation ofthese devices, modern communication networks have increased theircapabilities to support high bandwidth data connections, simultaneousvoice and data support, and other innovations to provide an “always on”networking capability for these devices.

Because these devices enjoy almost constant access to the Internet andcontinuously improving capabilities, many new tools and applicationshave been enabled and now are used by most modern consumers. Thecombination of a proliferation of these devices, applications for thesedevices, increases in computing power, and improvement in connectivitycapabilities of these devices has resulted in an overall advancement oftechnology that has enabled new interactions between users andinformation. Many tasks are now done using smartphones or other portablecomputing devices that until recently were either done manually or usingdedicated desktop computer.

SUMMARY

The present disclosure is directed to detecting and using mood-conditionaffinities (also referred to herein simply as an “affinity”). As usedherein, an “affinity” can be used to refer to an association between acondition and a mood. The affinities can be determined by detectingevents at various devices, determining conditions when the events aredetected, and determining a mood associated with the event. Varioustypes of data can be used to determine the conditions and mood, and theaffinities can be generated based on these data. The affinities can bestored and used to project mood and/or for other purposes.

A computing device such as a smartphone can access sensors and/oroff-board devices to collect sensor readings. The sensor readings can beanalyzed by an affinity application or affinity service to determineconditions at or near the computing device. The sensors and/or off-boardsensors also can capture biometric data associated with a user or otherentity. The biometric data can be analyzed by the affinity applicationor the affinity service to determine a mood and/or emotion (“mood”)associated with the user or other entity. The mood can be associatedwith the conditions to create an affinity between certain moods andconditions. Affinity data can be generated to relay these affinities (oraspects of the affinities) to users or other entities. The affinity datacan be used for various personal and/or business purposes. In someembodiments, the affinity data can be used to help improve mood; toavoid conditions or events that tend to negatively impact mood; to planfor interactions, transactions, or events with certain people, places,or things; and/or for other purposes.

According to one aspect of the concepts and technologies disclosedherein, a system is disclosed. The system can include a processor and amemory. The memory can store computer-executable instructions that, whenexecuted by the processor, cause the processor to perform operations.The operations can include obtaining collected data associated with auser device. The collected data can include sensor readings collected bythe user device. The operations also can include determining a conditionat the user device and a mood associated with the condition, generatingan affinity that defines a relationship between the condition and themood, and storing the affinity at a data storage device.

In some embodiments, the computer-executable instructions, when executedby the processor, cause the processor to perform additional operations.The additional operations can include detecting an event associated withthe user device and requesting the collected data in response todetecting the event. In some embodiments, the system also can includesensors located at the user device and off-board devices incommunication with the user device. The off-board devices can include acamera and the sensors can include biometric sensors. In someembodiments, the collected data further can include biometric data.Determining the mood can include analyzing the biometric data todetermine the mood.

In some embodiments, determining the mood can include comparing thebiometric data to mood information stored with the affinity anddetermining, based upon the comparing, the mood. In some embodiments,the computer-executable instructions, when executed by the processor,cause the processor to perform additional operations. The additionaloperations can include receiving, from a requestor, a request foraffinity data; determining another condition that is associated with therequestor; identifying another affinity associated with the othercondition; and providing the affinity data to a recipient, the affinitydata being based upon the other affinity.

In some embodiments, providing the affinity data to the recipient caninclude providing a social networking status update to the recipient.The social networking status update can indicate the further conditionand a further mood projected for the requestor. In some embodiments,providing the affinity data to the recipient can include providing analert that relates to an event to the requestor. The event can beassociated with the requestor. In some embodiments, receiving therequest for the affinity data includes obtaining further collected datafrom the requestor; determining the further condition; and determining,by the processor and based on the further condition, that affinity datashould be provided to the recipient.

According to another aspect of the concepts and technologies disclosedherein, a computer storage medium is disclosed. The computer storagemedium can have computer-executable instructions stored thereon. Whenthe computer-executable instructions are executed by a processor, theprocessor can perform operations including obtaining collected dataassociated with a user device. The collected data can include sensorreadings collected by the user device. The operations also can includedetermining a condition at the user device and a mood associated withthe condition; generating an affinity that defines a relationshipbetween the condition and the mood; and storing the affinity at a datastorage device.

In some embodiments, the collected data further can include biometricdata. Determining the mood can include analyzing the biometric data todetermine the mood. In some embodiments, the computer-executableinstructions, when executed by the processor, cause the processor toperform operations that further can include receiving, from a requestor,a request for affinity data; determining a further condition that isassociated with the requestor; identifying a further affinity associatedwith the further condition; and providing the affinity data to arecipient, the affinity data being based upon the further affinity. Insome embodiments, receiving the request for the affinity data caninclude obtaining further collected data from the requestor; determiningthe further condition; and determining, by the processor and based onthe further condition, that affinity data should be provided to therecipient.

According to yet another aspect, a method is disclosed. The method caninclude obtaining, at a processor that executes an affinity service,collected data associated with a user device. The collected data caninclude sensor readings collected by the user device. The method alsocan include determining, by the processor, a condition at the userdevice and a mood associated with the condition; generating, by theprocessor, an affinity that defines a relationship between the conditionand the mood; and storing, by the processor, the affinity at a datastorage device.

In some embodiments, the collected data further can include biometricdata and determining the mood can include analyzing the biometric datato determine the mood. In some embodiments, determining the mood caninclude comparing the biometric data to mood information stored with theaffinity and determining, based upon the comparing, the mood. In someembodiments, the method also can include receiving, by the processor andfrom a requestor, a request for affinity data; determining, by theprocessor, a further condition that is associated with the requestor;identifying, by the processor, a further affinity associated with thefurther condition; and providing, by the processor, the affinity data toa recipient, the affinity data being based upon the further affinity.

In some embodiments, providing the affinity data to the recipient caninclude providing a social networking status update to the recipient.The social networking status update can indicate the further conditionand a further mood projected for the requestor. In some embodiments,providing the affinity data to the recipient can include providing analert that relates to an event to the requestor. The event can beassociated with the requestor. In some embodiments, receiving therequest for the affinity data can include obtaining, by the processor,further collected data from the requestor; determining, by theprocessor, the further condition; and determining, by the processor andbased on the further condition, that affinity data should be provided tothe recipient.

Other systems, methods, and/or computer program products according toembodiments will be or become apparent to one with skill in the art uponreview of the following drawings and detailed description. It isintended that all such additional systems, methods, and/or computerprogram products be included within this description, be within thescope of this disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a system diagram illustrating an illustrative operatingenvironment for various embodiments of the concepts and technologiesdescribed herein.

FIG. 2 is a flow diagram showing aspects of a method for creatingaffinities, according to an illustrative embodiment of the concepts andtechnologies described herein.

FIG. 3 is a flow diagram showing aspects of a method for providingaffinity data to a requestor, according to an illustrative embodiment ofthe concepts and technologies described herein.

FIG. 4 is a flow diagram showing aspects of a method for projecting amood using affinity data, according to an illustrative embodiment of theconcepts and technologies described herein.

FIGS. 5A-5H are user interface diagrams showing various screen displaysfor detecting, providing, and using mood-condition affinities, accordingto some illustrative embodiments of the concepts and technologiesdescribed herein.

FIG. 6 schematically illustrates a network, according to an illustrativeembodiment of the concepts and technologies described herein.

FIG. 7 is a block diagram illustrating an example computer systemconfigured to detect and use mood-condition affinities, according tosome illustrative embodiments of the concepts and technologies describedherein.

FIG. 8 is a block diagram illustrating an example mobile deviceconfigured to detect and use mood-condition affinities and/or tointeract with the affinity service, according to some illustrativeembodiments of the concepts and technologies described herein.

DETAILED DESCRIPTION

The following detailed description is directed to detecting and usingmood-condition affinities. A computing device such as a smartphone canaccess sensors and/or off-board devices to collect sensor readings. Thesensors and/or off-board sensors also can capture biometric dataassociated with a user or other entity. The sensor readings andbiometric data can be analyzed at the computing device or provided toanother device or service such as, for example, an affinity service thatcan be hosted and/or executed by a server computer or other device. Theaffinity service or an affinity application executed by the computingdevice can analyze the sensor readings to determine conditions at ornear the computing device. The affinity service or affinity applicationalso can analyze the biometric data to determine a mood and/or emotion(“mood”) associated with the user or other entity. The mood can beassociated with the conditions to create affinities between certainmoods and conditions. The affinities can be stored in a manner that issearchable by any condition associated with the affinity.

When events are detected at a device, conditions associated with theevent can be determined and used to search the affinities. Affinity datacan be generated to relay relationships between the conditions and moodto users or other entities. The affinities also can be used to projectmood based on the conditions. Thus, embodiments of the concepts andtechnologies described herein can be used to provide insight into howcertain events, conditions, locations, times at locations, transactions,interactions, and/or other activities can affect mood of a user or otherentity, to project mood based on upcoming or detected events, and forother purposes. Embodiments of the concepts and technologies describedherein also can be used to provide information for improving mood ofusers or other entities and/or otherwise providing insight into variousactivities.

While the subject matter described herein is presented in the generalcontext of program modules that execute in conjunction with theexecution of an operating system and application programs on a computersystem, those skilled in the art will recognize that otherimplementations may be performed in combination with other types ofprogram modules. Generally, program modules include routines, programs,components, data structures, and other types of structures that performparticular tasks or implement particular abstract data types. Moreover,those skilled in the art will appreciate that the subject matterdescribed herein may be practiced with other computer systemconfigurations, including hand-held devices, multiprocessor systems,microprocessor-based or programmable consumer electronics,minicomputers, mainframe computers, and the like.

Referring now to FIG. 1, aspects of an operating environment 100 forvarious embodiments of the concepts and technologies disclosed hereinfor detecting and using mood-condition affinities will be described,according to an illustrative embodiment. The operating environment 100shown in FIG. 1 includes a server computer 102. The server computer 102can operate in communication with and/or as part of a communicationsnetwork (“network”) 104, though this is not necessarily the case in allembodiments and/or at all times.

According to various embodiments, the functionality of the servercomputer 102 may be provided by one or more server computers, desktopcomputers, mobile telephones, laptop computers, set-top boxes, othercomputing systems, and the like. It should be understood that thefunctionality of the server computer 102 can be provided by a singledevice, by two similar devices, and/or by two or more dissimilardevices. For purposes of describing the concepts and technologiesdisclosed herein, the server computer 102 is generally described hereinas a single server computer as one example embodiment that is easy todescribe and to understand. It should be understood that this embodimentis illustrative, and should not be construed as being limiting in anyway.

The server computer 102 can execute an operating system (not shown inFIG. 1) and one or more application programs such as, for example, anaffinity service 106. The operating system can include a computerprogram that can control the operation of the server computer 102. Theaffinity service 106 can include an executable program that can beconfigured to execute on top of the operating system to provide variousfunctions as illustrated and described herein. Before explaining thefunctionality of the affinity service 106, various other devices andentities shown in the operating environment 100 illustrated in FIG. 1will be described.

The operating environment 100 also can include a user device 108. Theuser device 108 can include various types of computing devices.According to various embodiments of the concepts and technologiesdescribed herein, the functionality of the user device 108 may beprovided by one or more mobile telephones, smartphones, tabletcomputers, slate computers, laptop computers, smart watches or otherwearable computing devices, media players, other computing devices, andthe like. It should be understood that the functionality of the userdevice 108 can be provided by a single device, by two similar devices,and/or by two or more dissimilar devices. For purposes of describing theconcepts and technologies disclosed herein, the user device 108 isgenerally described herein as a smartphone. Based on the above, itshould be understood that this embodiment is illustrative, and shouldnot be construed as being limiting in any way.

The user device 108 can include one or more sensors 110. According tovarious embodiments of the concepts and technologies described herein,the sensors 110 can include a diverse set of sensors and/or sensingdevices. The sensors 110 can be used in accordance with the concepts andtechnologies described herein to determine conditions associated with auser, a user device 108, and/or an area associated with a user or userdevice 108. Various contemplated sensors that can be included in thesensors 110 are illustrated and described herein, but should not beviewed as limiting. Briefly, the sensors 110 can include, but are notlimited to, location sensors, time devices, proximity sensors, lightsensors, audio sensors, heart rate sensors, pulse oximeters (“PulseOx”),sphygmomanometers, facial expression detectors, movement and/ororientation sensors, voice recognition devices, thermometers,barometers, humidity sensors, anemometers, vibration detection sensors,combinations thereof, or the like. These and other sensors will bediscussed in more detail herein.

The user device 108 also can execute an operating system (not shown inFIG. 1) and one or more application programs such as, for example, anaffinity application 112. The operating system can include a computerprogram that can control the operation of the user device 108 and theaffinity application 112 can include an executable program that can beconfigured to execute on top of the operating system to provide variousfunctions as illustrated and described herein.

According to various embodiments, the user device 108 can be configured,via execution of the affinity application 112 and/or othercomputer-executable instructions, to collect sensor readings and/orconditions information using the sensors 110 and/or other devices suchas, for example, off-board devices 114. The off-board devices 114 caninclude various sensors including, but not limited to, those mentionedabove with reference to the sensors 110. For example, the off-boarddevices 114 can include cameras, proximity sensors, various biometricdevices, location devices, proximity sensors, payment systems (fordetecting transactions or the like), combinations thereof, or the like.The off-board devices 114 also can include other types of sensors ordevices such as location beacons, timers, traffic sensors, proximitysensors, and/or other devices including but not limited to thoseillustrated and described herein.

According to various embodiments, the off-board devices 114 can be ownedand/or operated by (or at least accessible to) an entity that cancontrol or offer the affinity service 106. In some contemplatedembodiments, an entity that owns and/or operates the affinity service106 can contract with various entities to access the off-board devices114. When the user device 108 is in a vicinity of the off-board devices114, for example in an environment 116 in which the user device 108 islocated, the off-board devices 114 can be made available to the userdevice 108 and/or other entities to enable collection of sensorreadings, audio data, video data, time information (e.g., duration at alocation, duration involved in a transaction, etc.), locationinformation, proximity information, biometric data, traffic information,and/or other types of data or information for use as illustrated anddescribed herein. In some other embodiments, the off-board devices 114can include wearable sensor arrays and/or wearable devices that can belocated on or near the user or other entity. In yet other embodiments,the off-board devices 114 can include combinations of the above. Itshould be understood that these examples are illustrative and thereforeshould not be construed as being limiting in any way.

The affinity application 112 can be configured to monitor conditions,states, and events associated with a user or other entity (labeled“user” in FIG. 1) and/or an environment 116 in which the user device 108and/or the user are located. According to various embodiments of theconcepts and technologies described herein, the affinity application 112can be executed by the user device 108 to detect events associated withthe user device 108. These events can be detected in a number of mannerssuch as, for example, detecting calendar events; detecting changes instate, location, or the like; detecting time at a location and/or intransaction; detecting an explicit indication of an event; detectingproximity to other users; detecting music; detecting audio levels;detecting weather conditions; detecting transactions; combinationsthereof; or the like.

According to various embodiments of the concepts and technologiesdescribed herein, an “event” is defined as a change in a stateassociated with a user or other entity. Thus, if a user or other entitymoves to, from, and/or within a location; interacts with a certainperson; hears music; eats a certain food; drinks a certain drink;engages in a particular transaction; attends a particular social event;has a particular facial expression; moves; stops moving; has particularvital signs; or the like; an event can be determined to have occurred bythe affinity application 112 and/or the affinity service 106, as will beexplained in more detail below. According to various embodiments of theconcepts and technologies described herein, the affinity application 112can be configured to detect events, to define information that candefine events, and to collect data such as sensor readings, location,weather data, etc. when the events are detected. According to variousembodiments of the concepts and technologies described herein, theaffinity application 112 can be configured to collect informationdefining conditions at or near the environment 116 and provide theinformation to the affinity service 106 as the collected data 118.

As shown in FIG. 1, the collected data 118 can include, but is notlimited to, location data (e.g., geographic coordinates that define alocation, places of business associated with the location, contactinformation associated with the location, and the like); event data(e.g., types of events detected such as entering a place of business,being involved with a transaction, going to sleep, speaking on thephone, or the like); sensor data (e.g., sensor readings associated withone or more of the sensors 110 and/or the off-board devices 114);weather data (e.g., temperature, pressure, wind speed, light levels,humidity, and the like); proximity information (e.g., devices, people,objects, or other entities near the user device 108); biometric data(e.g., heart rate, blood pressure, oxygen saturation, fluctuations inbiometric readings, or the like); and/or other information (e.g., facialexpressions, time information, duration information, keyword detectionin spoken words, or the like). These and other types of information canbe collected by the user device 108 (e.g., via execution of the affinityapplication 112) via the sensors 110 and/or the off-board devices 114.The collected data 118 can be provided to the server computer 102 by theuser device 108 and used as illustrated and described herein by theaffinity service 106. It should be understood that this example isillustrative and therefore should not be construed as being limiting inany way.

According to various embodiments, the affinity service 106 can beconfigured to obtain the collected data 118 (or recognize receipt of thecollected data 118). The affinity service 106 can be configured toanalyze the collected data 118 to determine one or more affinities 120associated with the user device 108 (or user or other entity associatedwith the user device 108). As used herein, an “affinity” refers to arelationship between an event or condition (as these terms are definedherein) associated with the user device 108 and a mood (as definedherein). Thus, an affinity 120 can define a mood (calm, agitated, upset,angry, or the like) for various types of events or conditions such aspresence of a particular person in the environment 116 (e.g., aproximity of the user device 108), music that can be heard in theenvironment 116, transactions being completed or performed at the userdevice 108, a location associated with the environment 116, places ofbusiness at or near the environment 116, calendar events and/or calendarevent descriptions, weather conditions, types of food or drink consumedby a user or other entity, activities or types of activities, trafficconditions, activities, combinations thereof, or the like.

It can be appreciated that a “mood” can be subjective. As such, theconcepts and technologies described herein can be used to define a“mood” in objective terms. In particular, a “mood” as defined hereinrefers to an objectively detected or projected mood that is determinedbased upon collected data 118 and/or mood information that can be storedas part of one or more affinities 120 and/or elsewhere. The moodinformation can include definitions of particular moods for one or moreusers or other entities, and these moods can be defined for each user orother entity, in some embodiments. The mood therefore can be definedbased upon biometric information (e.g., heart rate, oxygen saturation,blood pressure, fluctuations in biometric readings—which can indicatestress levels in some embodiments, combinations thereof, or the like);facial expressions associated with the user or other entity; keywordanalysis (e.g., spoken words at or near the user device 108 can bemonitored since certain words or phrases may indicate a mood associatedwith a user or other entity); combinations thereof; or the like.

Moods for a particular user can be defined based on various criteria,conditions, and the like, any or all of which may be defined by users orother entities. Some example user interfaces for defining moods areillustrated and described herein, particularly with reference to FIGS.5G-5H. Regardless of how the moods are defined, the affinity service 106can be configured to store the affinities 120. The affinities 120 canassociate the defined moods with one or more events and/or conditionsdetected when the events occurred. Thus, the affinities 120 cancorrespond to associations between moods and one or more conditionsassociated with one or more events. The conditions can include, but arenot limited to, locations (geographic locations, businesses or contactsat or near those locations, home or office locations, etc.); dates;times of day; weather conditions; proximity of people or objects; foodor drink being consumed, seen, or smelled; local landmarks or venues;types of meetings; people associated with certain calendar events;social relationships with other people; time durations at locations orinvolved in transactions; combinations thereof, or the like. Thus, theaffinities 120 can store past information associating conditions withmood. The affinities 120 can therefore be used by the affinity service106 to identify or project moods when conditions are detected. Becausethe affinities 120 can be used for additional and/or alternativepurposes, it should be understood that these examples are illustrativeand therefore should not be construed as being limiting in any way.

According to various embodiments of the concepts and technologiesdescribed herein, the affinities 120 can be stored in a data storagedevice such as a data store 122. The functionality of the data store 122can be provided by one or more databases, server computers, desktopcomputers, mobile telephones, laptop computers, other computing systems,and the like. In the illustrated embodiments, the functionality of thedata store 122 can be provided by a database that can be stored by theserver computer 102 and/or hosted by another data storage device that isremote from the server computer 102. It should be understood that thisexample is illustrative and therefore should not be construed as beinglimiting in any way.

The affinity service 106 can be configured to receive a request foraffinity data (“affinity data request”) 124. The affinity data request124 can be generated by the user device 108 and/or other devices. Insome other embodiments, the affinity service 106 can effectivelygenerate the affinity data request 124 upon detecting an eventassociated with the user or other entity. Thus, the affinity datarequest 124 can be generated by the user device 108, the affinityservice 106, and/or other entities. In some embodiments, the affinityservice 106 can periodically obtain the collected data 118 from the userdevice 108. The affinity service 106 can detect, based upon an analysisof the collected data 118, an event associated with the user device 108.This detection can correspond, in various embodiments, to the affinitydata request 124. Regardless of how the affinity data request 124 isobtained, the affinity service 106 can be configured to determine anevent associated with the user device 108 in response to the affinitydata request 124. It should be understood that this example isillustrative and therefore should not be construed as being limiting inany way.

The affinity service 106 can query the affinities 120 and identify moodsand/or conditions that are associated with the event detected inassociation with the user device 108. The affinity service 106 cangenerate affinity data 126 based upon the identified affinities 120.Thus, the affinity service 106 can generate affinity data 126 that canindicate a defined mood associated with various events and/orconditions. The affinity service 106 can provide the affinity data 126to the user device 108 and/or to one or more other systems and devices128.

According to various embodiments, the affinity data 126 can be providedas an alert to the user device 108. The alert can indicate affinityinformation such as moods or the like associated with a detectedcondition or event. Thus, the alert can inform a user that a particularmood is projected based on an event or condition. The alert also canprovide information related to an event or condition such as, forexample, that a particular person has certain likes or dislikes, etc.These and other aspects of providing alerts using the affinity service106 will be illustrated and described in more detail below, particularlywith reference to FIGS. 2-5H. The affinity data 126 also can correspondto a social networking status update (“status update”), which can begenerated based upon detected moods and/or conditions as illustrated anddescribed in more detail herein. Thus, the other systems and devices 128can include social networking services, or the like. It should beunderstood that this example is illustrative and therefore should not beconstrued as being limiting in any way.

In practice, the user device 108 and/or the affinity application 112executed by the user device 108 can detect an event. The event can bedetected based on various data sources (e.g., calendar events,application data, web activity, or the like) and/or activity detected atthe user device 108. When an event is detected by the user device 108,the user device 108 can collect sensor readings and/or other types ofdata from one or more of the sensors 110 and/or one or more availableoff-board devices 114. The user device 108 can provide the collecteddata 118 to the affinity service 106 for analysis. It should beunderstood that the functionality of the affinity service 106illustrated and described herein can also be provided by the affinityapplication 112. Thus, the affinity service 106 can operate as a moduleexecuted by the user device 108 in some embodiments, thereby allowingsome embodiments to function without the illustrated the server computer102. It should be understood that this example is illustrative andtherefore should not be construed as being limiting in any way.

The affinity service 106 can analyze the collected data 118 anddetermine, based upon the analysis, one or more conditions at or nearthe user device 108 (e.g., in the environment 116) and a mood associatedwith a user or other entity. The affinity service 106 can generate theaffinities 120. The affinities 120 can include data associations betweenthe mood and the one or more conditions. The affinities 120 can bestored in a searchable manner so that the affinities 120 can be searchedby any associated condition. The mood can be determined based upon ananalysis of the biometric data and/or other information (e.g., facialexpressions, detected laughter, detected crying, detected stress levels,keyword detection, combinations thereof, or the like), as explainedabove. In some embodiments, the data store 122 also can store mood data130, which can define one or more moods by defining ranges for biometricdata and/or other data points that can be used to determine mood. It canbe appreciated that the mood data 130 can include, but is not limitedto, the information mentioned herein with respect to “mood information.”An example user interface for creating the mood data 130 will beillustrated and described in more detail herein, particularly withreference to FIGS. 5G-5H.

An event can be detected at or in association with the user device 108.The event can be detected in a variety of ways as explained above indetail. Regardless of how the events are detected, the user device 108can obtain another iteration of the collected data 118 and provide thecollected data 118 to the affinity service 106. The affinity service 106can again analyze the collected data 118 to determine conditionsassociated with the user device 108. One or more of the conditions canbe used to search the affinities 120. Affinities 120 that shareconditions with the detected conditions can be identified and affinitydata 126 that projects a mood can be generated and used for variouspurposes. In some other embodiments, a request for affinity data 126 canbe received by the affinity service 106 and the affinity data 126 can beidentified based on expected conditions. Thus, a projected mood and/orother types of affinity data 126 can be identified and used inaccordance with various embodiments of the concepts and technologiesdescribed herein.

FIG. 1 illustrates one server computer 102, one network 104, one userdevice 108, and one data store 122. It should be understood, however,that various implementations of the operating environment 100 caninclude zero, one, or more than one server computer 102; zero, one, ormore than one network 104; zero, one, or more than one user device 108;and/or zero, one, or more than one data store 122. As such, theillustrated embodiment should be understood as being illustrative, andshould not be construed as being limiting in any way.

Turning now to FIG. 2, aspects of a method 200 for creating affinities120 will be described in detail, according to an illustrativeembodiment. It should be understood that the operations of the methodsdisclosed herein are not necessarily presented in any particular orderand that performance of some or all of the operations in an alternativeorder(s) is possible and is contemplated. The operations have beenpresented in the demonstrated order for ease of description andillustration. Operations may be added, omitted, and/or performedsimultaneously, without departing from the scope of the concepts andtechnologies disclosed herein.

It also should be understood that the methods disclosed herein can beended at any time and need not be performed in its entirety. Some or alloperations of the methods, and/or substantially equivalent operations,can be performed by execution of computer-readable instructions includedon a computer storage media, as defined herein. The term“computer-readable instructions,” and variants thereof, as used herein,is used expansively to include routines, applications, applicationmodules, program modules, programs, components, data structures,algorithms, and the like. Computer-readable instructions can beimplemented on various system configurations including single-processoror multiprocessor systems, minicomputers, mainframe computers, personalcomputers, hand-held computing devices, microprocessor-based,programmable consumer electronics, combinations thereof, and the like.

Thus, it should be appreciated that the logical operations describedherein are implemented (1) as a sequence of computer implemented acts orprogram modules running on a computing system and/or (2) asinterconnected machine logic circuits or circuit modules within thecomputing system. The implementation is a matter of choice dependent onthe performance and other requirements of the computing system.Accordingly, the logical operations described herein are referred tovariously as states, operations, structural devices, acts, or modules.These states, operations, structural devices, acts, and modules may beimplemented in software, in firmware, in special purpose digital logic,and any combination thereof. As used herein, the phrase “cause aprocessor to perform operations” and variants thereof is used to referto causing a processor of a computing system or device, such as theserver computer 102 or the user device 108 to perform one or moreoperations and/or causing the processor to direct other components ofthe computing system or device to perform one or more of the operations.

For purposes of illustrating and describing the concepts of the presentdisclosure, the methods disclosed herein are described as beingperformed by the server computer 102 and/or the user device 108 viaexecution of one or more software modules such as, for example, theaffinity service 106 and/or the affinity application 112. It should beunderstood that additional and/or alternative devices and/or networknodes can provide the functionality described herein via execution ofone or more modules, applications, and/or other software including, butnot limited to, the affinity service 106 and/or the affinity application112. Thus, the illustrated embodiments are illustrative, and should notbe viewed as being limiting in any way.

The method 200 begins at operation 202. At operation 202, the servercomputer 102 can detect an event associated with a device such as theuser device 108. As explained above in detail, the server computer 102can detect an event as shown in operation 202 in various manners. Insome embodiments, for example, the server computer 102 can obtain thecollected data 118 from a user device 108 and determine, based uponanalyzing the collected data 118, that an event has occurred. Thus,operation 202 can include, in some embodiments, the server computer 102obtaining the collected data 118 and analyzing the collected data 118 asillustrated and described above with reference to FIG. 1.

In some other embodiments, the user device 108 can determine that anevent has occurred and provide the collected data 118 to the servercomputer 102. The user device 108 can determine that the event hasoccurred based upon detecting, and/or detecting a change in, a location,a weather condition, an audio condition (e.g., music playing, an ambientsound level, etc.), a light condition, a calendar event, a meeting, anactivity, a travel condition, a transaction, combinations thereof, orthe like. In some embodiments, the server computer 102 can determine,based upon receiving the collected data 118, that an event has occurredat the user device 108.

In some embodiments, the user device 108 can detect the event andprovide the collected data via execution (by the affinity application112) of a routine 203. The routine 203 can include the operationsillustrated in FIG. 2 and/or additional and/or alternative operations.As such, it should be understood that the routine 203 is illustrative ofthe concepts and technologies described herein and that the routine 203is not limited to the illustrated embodiment.

In the illustrated embodiment, the user device 108 can detect an event,as shown at operation 203A. As noted above, the user device 108 candetect the event by detecting calendar events, locations, local users,audio levels, light levels, application usage, transactions, weatherconditions, other conditions, combinations thereof, or the like. Inresponse to detecting the event, the user device 108 can collect datavia the sensors 110 and/or the off-board devices 114, as shown atoperation 203B. The user device 108 can package the data collected inoperation 203B as the collected data 118 and provide the collected data118 to the affinity service 106 as shown at operation 203C. Because thecollected data 118 can be collected and/or provided to the servercomputer 102 in additional and/or alternative ways, it should beunderstood that the illustrated routine 203 is illustrative and shouldnot be construed as being limiting in any way.

In some embodiments of the method 200, the routine 203 illustrated anddescribed herein may not be performed and/or may be omitted. As such,operation 202 can correspond to the server computer 102 analyzing thecollected data 118, which can be provided at various times, anddetecting an event associated with the user device 108. It should beunderstood that this example is illustrative and therefore should not beconstrued as being limiting in any way.

From operation 202, the method 200 can proceed to operation 204. Atoperation 204, the server computer 102 can determine conditionsassociated with the user device 108. In operation 204, the servercomputer 102 can analyze the collected data 118 and determine, basedupon the collected data 118, one or more conditions associated with theuser device 108. Thus, operation 204 can include the server computer 102analyzing the collected data 118 and determining one or more conditionsbased on data points in the collected data 118. Thus, for example, theserver computer 102 can determine a location defined by the collecteddata 118, a temperature defined by the collected data 118, a user orobject at or near the user device 108 as defined by the collected data118, combinations thereof, other conditions, or the like. It can beappreciated with reference to FIG. 1 and the description of thecollected data 118 in FIG. 1 that the conditions can include any sensorreadings, data, or information illustrated and described with referenceto the collected data 118. In operation 204, the server computer 102 candetermine these data points and determine conditions based on these datapoints. As such, the above-mentioned examples of the conditions shouldbe understood as being illustrative and should not be construed as beinglimiting in any way.

From operation 204, the method 200 can proceed to operation 206. Atoperation 206, the server computer 102 can determine a mood. Accordingto various embodiments of the concepts and technologies describedherein, the server computer 102 can determine the mood at leastpartially based on the conditions determined in operation 204, thoughthis is not necessarily the case. The server computer 102 also candetermine the mood by identifying biometric data and/or otherinformation (e.g., facial expressions, keyword analysis, stress levels,or the like) included in the collected data 118 and comparing thisinformation to the mood data 130 illustrated and described herein. Thus,operation 206 can be performed, in some embodiments in conjunction withoperation 204, and as such, the server computer 102 may analyze thecollected data 118 to identify conditions and mood in a singleoperation, in some embodiments. It should be understood that thisexample is illustrative and therefore should not be construed as beinglimiting in any way.

From operation 206, the method 200 can proceed to operation 208. Atoperation 208, the server computer 102 can generate one or more affinity120. According to various embodiments of the concepts and technologiesdescribed herein, the affinity 120 generated in operation 208 caninclude one or more affinity between a condition detected in operation204 and one or more mood determined in operation 206. The one or moreaffinity 120 also can include and/or reflect other conditions associatedwith the event detected in operation 202. Thus, it should be appreciatedthat an affinity 120 generated in operation 208 may include at least arelationship between a mood and a condition. The affinity 120 generatedin operation 208 also can include a location, proximity to people orthings, transactions, event descriptions, other types of informationillustrated and described herein, and the like. According to variousembodiments, the affinities 120 can be generated as records or otherdata structures that can associate one or more conditions with one ormore moods. It should be understood that this example is illustrativeand therefore should not be construed as being limiting in any way.

From operation 208, the method 200 can proceed to operation 210. Atoperation 210, the server computer 102 can store the one or moreaffinities 120. Thus, in operation 210, the server computer 102 canstore the affinities 120 generated in operation 208. In someembodiments, the server computer 102 can store the affinities 120 at adata storage device such as, for example, the data store 122, thoughthis is not necessarily the case. According to various embodiments ofthe concepts and technologies described herein, the affinities 120 canbe catalogued and stored in a searchable format. Thus, the affinityservice 106 can be configured to query any aspect of the affinities 120such as, for example, mood or condition. These and other aspects ofmatching affinities 120 to conditions will be more clearly understoodwith reference to FIGS. 3-5H.

From operation 210, the method 200 can proceed to operation 212. Themethod 200 can end at operation 212.

Turning now to FIG. 3, aspects of a method 300 for providing affinitydata 126 to a requestor will be described in detail, according to anillustrative embodiment. The method 300 begins at operation 302. Atoperation 302, the server computer 102 can detect a request for affinitydata 126. According to various embodiments of the concepts andtechnologies described herein, the request for affinity data 126 cancorrespond to the affinity data request 124 illustrated and describedherein with reference to FIG. 1. Thus, it can be appreciated that therequest received in operation 302 can be received from the user device108, in some embodiments, while in some other embodiments, the affinitydata request 124 can be received from other entities. It should beunderstood that these examples are illustrative and therefore should notbe construed as being limiting in any way.

In various embodiments of the concepts and technologies describedherein, the request received in operation 302 can include at least onecondition. Thus, the request received in operation 302 can be implicitlydetermined to have been received by the server computer 102 by receivingthe collected data 118. In other words, in some embodiments of theconcepts and technologies described herein, the server computer 102 candetermine, based upon receiving the collected data 118, that affinitydata 126 is being requested and/or should be provided. It should beunderstood that these examples are illustrative and therefore should notbe construed as being limiting in any way. Regardless of how the requestin operation 302 is received (explicitly or implicitly), operation 302can correspond to the server computer 102 determining that affinity data126 should be provided to a recipient.

From operation 302, the method 300 can proceed to operation 304. Atoperation 304, the server computer 102 can determine conditionsassociated with the requestor. In some embodiments, the server computer102 can, in response to receiving the request in operation 302, obtainthe collected data 118 from the user device 108. In some otherembodiments, the server computer 102 may determine that the affinitydata 126 should be provided in response to receiving the collected data118. Regardless of whether the collected data 118 is obtained before orafter operation 302, the server computer 102 can determine, in operation304, one or more condition associated with the user device 108.

As explained above with reference to FIG. 2, the server computer 102 candetermine, in operation 304, one or more condition including, but notlimited to, a weather condition, an audio level condition, a light levelcondition, a transaction occurring, a local object or person, otherconditions, combinations thereof, or the like. Thus, operation 304 cancorrespond to the server computer 102 analyzing the collected data 118and identifying one or more condition associated with the user device108. It should be understood that this example is illustrative andtherefore should not be construed as being limiting in any way.

From operation 304, the method 300 can proceed to operation 306. Atoperation 306, the server computer 102 can identify one or moreaffinities 120 associated with the conditions determined in operation304. Thus, in operation 306, the server computer 102 can query theaffinities 120 using one or more of the determined conditions toidentify affinities 120 that are related to the one or more conditions.In some embodiments, the server computer 102 determines, in operation304, each condition associated with the collected data 118, and queries,in operation 306, the affinities 120 using each of the conditionsdetermined. Thus, it can be appreciated that the server computer 102 candetermine, in some embodiments of operation 306, one affinity 120 percondition (if stored). It should be understood that this example isillustrative and therefore should not be construed as being limiting inany way.

From operation 306, the method 300 can proceed to operation 308. Atoperation 308, the server computer 102 can provide affinity data 126 toa recipient. Thus, operation 308 can include the server computer 102generating the affinity data 126 based upon the affinities identified inoperation 306 and providing the affinity data 126 to a recipient. Itshould be understood that the recipient need not be the same entity thatrequested the affinity data 126, in some embodiments, while in otherembodiments the requestor and the recipient may be the same entity.

In particular, in one contemplated embodiment, the user device 108 canrequest the affinity data 126 in operation 302. The affinity data 126can include a social networking update. The social networking update canbe provided to the user device 108 or to a social networking service orother recipient. Thus, it can be appreciated using this simple examplethat the recipient and the requestor need not be the same entity.

In some other embodiments, the requestor and the recipient can be thesame entity. Thus, for example, the user device 108 may request theaffinity data 126 (explicitly or implicitly), and the affinity data 126can be provided to the user device 108 in operation 308. According tovarious embodiments, the affinity data 126 can be provided as an alert,as part of a display, or in other formats. Various example embodimentsfor providing the affinity data 126 to various entities will beillustrated and described in more detail herein with reference to FIGS.5A-5F.

In some embodiments, the affinity data 126 can be provided to the userdevice 108 as part of graphics data that, when rendered by the userdevice 108, causes the user device 108 to display one or more affinities120 and/or components thereof such as moods, conditions, or the like.Because other recipients and requestors are contemplated, and becausethe affinity data 126 can be provided in a variety of formats, it shouldbe understood that these examples are illustrative and therefore shouldnot be construed as being limiting in any way.

From operation 308, the method 300 can proceed to operation 310. Themethod 300 can end at operation 310.

Turning now to FIG. 4, aspects of a method 400 for projecting a moodusing affinity data 126 will be described in detail, according to anillustrative embodiment. The method 400 begins at operation 402. Atoperation 402, the server computer 102 can detect a request for affinitydata 126. According to various embodiments of the concepts andtechnologies described herein, operation 402 can be, but is notnecessarily, similar to operation 302 illustrated and described herein.Thus, it should be understood that the request detected in operation 402can be explicitly made by a requestor and/or implicitly determined tohave been made by analyzing collected data 118. It should be understoodthat these examples are illustrative and therefore should not beconstrued as being limiting in any way.

From operation 402, the method 400 can proceed to operation 404. Atoperation 404, the server computer 102 can obtain collected data 118associated with the requestor. As explained above with reference tooperation 304 of the method 300 illustrated and described in FIG. 3, thecollected data 118 can be provided by the user device 108 beforeoperation 402 and/or as part of operation 404. Thus, the server computer102 can request the collected data 118 from the user device 108 andreceive the collected data 118 from the user device 108 in operation404, in some embodiments, while in some other embodiments the userdevice 108 may provide the collected data 118 to the server computer 102before operation 402 or 404. At any rate, the server computer 102 canobtain the collected data 118.

From operation 404, the method 400 can proceed to operation 406. Atoperation 406, the server computer 102 can identify affinities 120 thatare related to the collected data 118. Thus, in operation 406, theserver computer 102 can analyze the collected data 118 to identify oneor more conditions associated with the user device 108. Based upon theone or more conditions, the server computer 102 can query the affinities120 to identify moods and/or conditions (stored as part of theaffinities 120) that are relevant to, correspond to, and/or areassociated with the determined conditions. In some embodiments of themethod 400, the server computer 102 can identify each conditionrepresented by the collected data 118 and query the affinities 120 basedon each condition. It should be understood that this example isillustrative and therefore should not be construed as being limiting inany way.

From operation 406, the method 400 can proceed to operation 408. Atoperation 408, the server computer 102 can project a mood based upon theaffinities 120 identified in operation 406. Thus, in operation 408, theserver computer 102 can analyze one or more (or each) of the affinities120 identified in operation 406 and identify a mood represented by eachaffinity 120. Thus, in some embodiments the server computer 102 can beconfigured to determine multiple moods and project a most likely mood inoperation 408 based on further analysis of the multiple moods.

In some embodiments, for example, if two different moods can beidentified. The server computer 102 can be configured to determine amost likely mood of the two different moods based on various factors(e.g., certain conditions may be more likely to affect a mood than otherconditions and as such, a mood associated with the condition that ismore likely to affect mood may be determined to be most likely). In onecontemplated example, the server computer 102 can determine a mood (ofmultiple moods that are possible) that has the most associatedconditions. For example, if the server computer 102 determines that fivedetermined conditions indicate mood number one and that one determinedcondition indicates mood number two, the server computer 102 maydetermine that mood number one is most likely. It should be understoodthat this example is illustrative and therefore should not be construedas being limiting in any way.

In some other embodiments, the server computer 102 can identify a mostlikely mood based upon a knowledge of what factors affect mood the most,as noted above, and as such any number of moods and/or conditions can beanalyzed to project a most likely mood based upon conditions. Regardlessof how the mood is determined by the identified affinities 120, theserver computer 102 can project the mood based on the affinities 120 andthe conditions determined to exist at the user device 108. It should beunderstood that this example is illustrative and therefore should not beconstrued as being limiting in any way.

From operation 408, the method 400 can proceed to operation 410. Atoperation 410, the server computer 102 can provide the mood informationto a recipient. As noted above, the requestor and the recipient can bedifferent entities and/or the same entity. The mood information can beprovided to a user device 108, for example, within an alert screen orother user interface. Alternatively, the mood information can beprovided to other entities that are unrelated to the requestor.Regardless of to whom the mood information is provided, variousembodiments of user interfaces for presenting affinity data 126 thatcaptures the mood information will be illustrated and described hereinin more detail with reference to FIGS. 5A-5H.

From operation 410, the method 400 can proceed to operation 412. Themethod 400 can end at operation 412.

FIGS. 5A-5H are user interface (“UI”) diagrams showing aspects of UIsfor using and/or interacting with an affinity service 106 and/or theaffinity application 112, according to some illustrative embodiments.FIG. 5A shows an illustrative screen display 500A. According to someembodiments of the concepts and technologies described herein, thescreen display 500A can be generated by a device such as the user device108 via interactions with the affinity service 106 and/or the affinityapplication 112. In particular, according to various embodiments, theuser device 108 can generate the screen display 500A and/or other screendisplays in conjunction with and/or based upon interactions with theaffinity application 112 described herein, which can be configured torender the screen display 500A using data generated at the user device108 and/or using data provided by the affinity service 106. It should beappreciated that the UI diagram illustrated in FIG. 5A is illustrativeof one contemplated example of the UIs that can be generated and/ordisplayed in accordance with the concepts and technologies disclosedherein, and therefore should not be construed as being limited in anyway.

According to various embodiments, the screen display 500A can bepresented, for example, when affinity data 126 is received by the userdevice 108 (e.g., prompted by detected events at the user device 108).Because the screen display 500A illustrated in FIG. 5A can be displayedat additional and/or alternative times, it should be understood thatthese examples are illustrative and therefore should not be construed asbeing limiting in any way.

The screen display 500A can include various menus and/or menu options(not shown in FIG. 5A). The screen display 500A also can include anaffinity service alert window 502. The affinity service alert window 502can be configured to provide the affinity data 126 illustrated anddescribed herein to a user or other entity. The affinity service alertwindow 502 can include various types of data and/or information that canbe included in the affinity data 126. Thus, as illustrated and describedherein, the affinity service alert window 502 can include event-basedinformation (“event information”) 504. The event information 504 canprovide context for the alert being provided by way of the affinityservice alert window 502. In the illustrated embodiment, the eventinformation 504 includes an indication that a calendar event (includinglocation, time, and participants) is about to occur. Thus, the eventinformation 504 can provide a context for the affinity data 126 beingprovided in relation to the corresponding event. It should be understoodthat this example is illustrative and therefore should not be construedas being limiting in any way.

As shown in FIG. 5A, the affinity service alert window 502 also includesaffinity information 506 that relates to the event. As shown in theexample embodiment illustrated in FIG. 5A, the affinity information 506indicates a preference associated with Jacob Josephson, a participant ina meeting (event). It should be understood that the illustrated affinityinformation 506 is illustrative, and that the affinity data 126 thatrelates to the participant can be any type of information illustratedand described herein. It also can be appreciated that the participant inthe illustrated embodiment may also be a user of the affinity service106 who has opted to share his affinities 120 and/or other informationsuch that the affinity data 126 can reflect his or her preferences,likes, etc., though this is not necessarily the case. It should beunderstood that this example is illustrative and therefore should not beconstrued as being limiting in any way.

The affinity service alert window 502 also can include a UI control 508to obtain more information. Selection of the UI control 508 can causethe user device 108 to present additional and/or alternative affinityinformation that relates to the event. Thus, selection of the UI control508 can present additional and/or alternative likes or dislikesassociated with the participant; mood and/or history informationassociated with a user or other entity associated with the user device108 and the location, time, and/or participant; other information;combinations thereof; or the like. The affinity service alert window 502also can include a UI control 510 to dismiss the affinity service alertwindow 502. Thus, for example, the user or other entity can select theUI control 510 to cause the user device 108 to close the affinityservice alert window 502 when the desired information has been obtainedvia the affinity service alert window 502, when the user or other entitywishes to close the affinity service alert window 502 for other reasons,and/or at other times at which the UI control 510 is selected.

The affinity service alert window 502 also can include a UI control 512to cancel the event and/or to cease obtaining information relevant tothe event. The UI control 512 may be selected, for example, if themeeting has been cancelled; if the user or other entity does not desireany other affinity information relevant to the event; or the like.Selection of the UI control 512 can cause the user device 108 to removethe event from the calendar; to cease recognizing the event as an eventfor purposes of obtaining affinity data 126 (e.g., by the affinityapplication 112); or the like. It can be appreciated that selection ofthe UI control 512 also can cause the user device 108 to hide theaffinity service alert window 502, though this is not necessarily thecase. Because additional or alternative controls can be included in theaffinity service alert window 502, it should be understood that theexample embodiment shown in FIG. 5A is illustrative and therefore shouldnot be construed as being limiting in any way.

Referring now to FIG. 5B, a UI diagram showing additional aspects ofsome of the concepts and technologies disclosed herein for providingand/or using an affinity service 106 and/or the affinity application 112is described in detail. In particular, FIG. 5B shows an illustrativescreen display 500B. According to various embodiments, the user device108 can generate the screen display 500B and/or other screen displays inconjunction with and/or based upon interactions with the affinityservice 106 and/or the affinity application 112 described herein (e.g.,via rendering data provided by the affinity service 106 and/or theaffinity application 112, or the like). In the illustrated embodiment,the screen display 500B can be presented, for example, in response todetecting a request to view events that a user or other entity enjoyed.Because the screen display 500B can be presented at additional and/oralternative times, it should be understood that this example isillustrative and therefore should not be construed as being limiting inany way. Also, it should be appreciated that the UI diagram illustratedin FIG. 5B is illustrative of one contemplated example of the UIs thatcan be generated and/or displayed in accordance with the concepts andtechnologies disclosed herein, and therefore should not be construed asbeing limited in any way.

The screen display 500B can include an enjoyed event display window 514.It should be understood that the enjoyed event display window 514 shownin FIG. 5B is one contemplated embodiment of a display that can be usedto display affinity data 126 such as events that were enjoyed by a useror other entity (e.g., a user of the user device 108). As such, theillustrated embodiment should not be construed as being limiting in anyway.

As shown in FIG. 5B, the enjoyed event display window 514 can provide anindication 516 of the types of affinity data 126 being displayed. Inthis case, as noted above, the enjoyed event display window 514 displaysinformation relating to enjoyed events, and as such, the indication 516can provide an explanation to this effect, though this is notnecessarily the case. The enjoyed event display window 514 also caninclude one or more enjoyed event information fields 518A-C (hereinaftercollectively and/or generically referred to as “enjoyed eventinformation fields 518”). The enjoyed event information fields 518 canprovide various types of information relating to events that weredetermined by the affinity service 106 and/or the affinity application112 as being enjoyable. As explained herein, the notion of what is“enjoyed” can generally be subjective, and as such, a user or otherentity can define objective standards by which moods can be determined(or at least projected) in accordance with the concepts and technologiesdescribed herein.

As shown in FIG. 5B, the enjoyed event information fields 518 candisplay information describing the events that were enjoyed. Forexample, the event information field 518A defines an associated event asa meeting at a certain date, time, and location with a certain person(in the illustrated embodiment, a meeting at 5367 West Main Street inAtlanta, Ga. on Dec. 1, 2015 at 9:04 through 9:13 AM). The enjoyed eventinformation fields 518 also can provide affinity data 126 associatedwith the event that corresponds to the enjoyed event information fields518. The example enjoyed event information field 518A also shows varioustypes of affinity data 126. In the example embodiment, the affinity data126 includes collected data 118 that was collected during the event andtherefore may have been determined to have an affinity with the mooddetected during the associated event. In this case, a music playing inthe background (“The Doors”); a drink being consumed (“coffee”); anactivity (engaging in charitable works); and a person with whom theentity or other user was meeting (“Eustice Jackson”) may have beendetermined to be related to the detected calm mood. It should beunderstood that this example is illustrative and therefore should not beconstrued as being limiting in any way.

As can be appreciated from the description of the concepts andtechnologies described herein, the enjoyed event information fields 518can provide any information that was determined to be (or projected tobe) related to the mood detected or projected at the time of thecorresponding events. Thus, some of the enjoyed event information fields518 indicate other people in a proximity of a user or other entity atthe time of the detected event (e.g., “your family” in the enjoyed eventinformation field 518B and “your spouse” in the enjoyed eventinformation field 518C); foods or drinks being consumed during themeetings (e.g., “coffee” in the enjoyed event information field 518A and“chicken marsala” in the enjoyed event information field 518B);locations (e.g., “5367 West Main Street, Atlanta, Ga.” in the enjoyedevent information field 518A and “home” in the enjoyed event informationfields 518B-C); and/or other information. Affinities 120 can be detectedbased on almost any detected conditions as illustrated and describedherein including, but not limited to, geographic location, time, date,other people, music being played, temperature or other weatherconditions, food or drink being consumed, transactions occurring,calendar events, other conditions, combinations thereof, or the like.Because various other conditions are illustrated and described hereinand can be used to detect affinities 120, it should be understood thatthese examples are illustrative and therefore should not be construed asbeing limiting in any way.

The enjoyed event display window 514 also can include a UI control 520.The UI control 520 can be selected to view more events that were enjoyedby a user or other entity (or interpreted to have been enjoyed). Thus,selection of the UI control 520 can cause the user device 108 to presentadditional and/or alternative enjoyed event information fields 518. Itshould be understood that additional enjoyed event information fields518 can also be accessed via scrolling a display (or panning with afinger or other input device), or the like. The enjoyed event displaywindow 514 also can include a UI control 522. The UI control 522 can beselected to view events that were not enjoyed by the user or otherentity (or interpreted to have not been enjoyed). Thus, selection of theUI controls 520, 522 can, but do not necessarily, cause the user device108 to hide the enjoyed event display window 514. Because additional oralternative controls can be included in the screen display 500B, itshould be understood that the example embodiment shown in FIG. 5B isillustrative and therefore should not be construed as being limiting inany way.

Referring now to FIG. 5C, a UI diagram showing additional aspects ofsome of the concepts and technologies disclosed herein for providingand/or using an affinity service 106 and/or the affinity application 112is described in detail. In particular, FIG. 5C shows an illustrativescreen display 500C. According to various embodiments, the user device108 can generate the screen display 500C and/or other screen displays inconjunction with and/or based upon interactions with the affinityservice 106 and/or the affinity application 112 described herein (e.g.,via rendering data provided by the affinity service 106 and/or theaffinity application 112, or the like). In the illustrated embodiment,the screen display 500C can be presented, for example, in response todetecting a request to view events that a user or other entity did notenjoy. For example, the screen display 500C can be presented in responseto detecting an interaction with the UI control 532 illustrated anddescribed above with reference to FIG. 5B, though this is notnecessarily the case. Because the screen display 500C can be presentedat additional and/or alternative times, it should be understood thatthese examples are illustrative and therefore should not be construed asbeing limiting in any way. Also, it should be appreciated that the UIdiagram illustrated in FIG. 5C is illustrative of one contemplatedexample of the UIs that can be generated and/or displayed in accordancewith the concepts and technologies disclosed herein, and thereforeshould not be construed as being limited in any way.

The screen display 500C can include an unenjoyable event display window524. It should be understood that the unenjoyable event display window524 shown in FIG. 5C is one contemplated embodiment of a display thatcan be used to display affinity data 126 such as events that were notenjoyed by a user or other entity (or events that were at leastunderstood to have not been enjoyed by the user or other entity such asa user of the user device 108). As such, the illustrated embodimentshould not be construed as being limiting in any way.

As shown in FIG. 5C, the unenjoyable event display window 524 canprovide an indication 526 of the types of affinity data 126 beingdisplayed. In this case, as noted above, the unenjoyable event displaywindow 524 displays information relating to events that were interpreted(or determined) to have not been enjoyed by a user or other entity. Assuch, the indication 526 can provide an explanation that one or moreevents that were not enjoyed by the user or other entity are beingdisplayed, though this is not required in all embodiments.

The unenjoyable event display window 524 can include one or moreunenjoyable event information fields 528A-C (hereinafter collectivelyand/or generically referred to as “unenjoyable event information fields528”). The unenjoyable event information fields 528 can provide varioustypes of information relating to events that were determined by theaffinity service 106 and/or the affinity application 112 as beingunenjoyable to the user or other entity (e.g., a user associated withthe user device 108). As noted above with respect to “enjoyed” events,notions of what is “unenjoyable” can also be subjective. Thus, as notedabove, users or other entities can define objective standards by whichmoods can be determined (or projected) in accordance with the conceptsand technologies described herein.

As shown in FIG. 5C, the unenjoyable event information fields 528 candisplay information describing the events that were perceived as notbeing enjoyed by the user or other entity. For example, the eventinformation field 528A defines an associated event as a “PerformanceReview” at a certain date, time, location, and participant. In theillustrated embodiment, a meeting at “Office” on Dec. 1, 2015 at 10:01AM through 10:32 AM with Jim Thorpe (who could be the user's or otherentity's boss, for example). The unenjoyable event information fields528 also can provide affinity data 126 associated with the event thatcorresponds to the unenjoyable event information fields 528.

The example unenjoyable event information field 528A also displaysaffinity data 126. In the example embodiment, the affinity data 126includes collected data 118 that was collected during the event andtherefore may have been determined to have an affinity with the mooddetected during the associated event. In the illustrated embodiments,participants or other entities detected at events, traffic conditions,or other information may have been determined to be related to thedetected agitated mood. It should be understood that these examples areillustrative and therefore should not be construed as being limiting inany way.

As can be appreciated from the description of the concepts andtechnologies described herein, the unenjoyable event information fields528 can provide any information that was determined to be (or projectedto be) related to the mood detected or projected at the time of thecorresponding events. Thus, some of the unenjoyable event informationfields 528 indicate other people in a proximity of a user or otherentity at the time of the detected event (e.g., “Jim Thorpe” in theunenjoyable event information fields 528A and 528C); traffic conditions(e.g., “heavier than usual” traffic and 3.4 times longer commute in theunenjoyable event information field 528B); locations (e.g., “Office” inthe unenjoyable event information field 528A and “home” in theunenjoyable event information field 528C); and/or other information.Affinities 120 can be detected based on almost any detected conditionsas illustrated and described herein including, but not limited to,geographic location, time, date, other people, music being played,temperature or other weather conditions, food or drink being consumed,transactions occurring, calendar events, combinations thereof, trafficconditions, delays, other conditions, or the like. Because various otherconditions are illustrated and described herein and can be used todetect affinities 120, it should be understood that these examples areillustrative and therefore should not be construed as being limiting inany way.

The unenjoyable event display window 524 also can include a UI control530. The UI control 530 can be selected to view more events that wereenjoyed by a user or other entity (or interpreted to have not beenenjoyed). Thus, selection of the UI control 530 can cause the userdevice 108 to present additional and/or alternative unenjoyable eventinformation fields 528. It should be understood that additionalunenjoyable event information fields 528 can also be accessed viascrolling a display (or panning with a finger or other input device), orthe like, as noted above with reference to FIG. 5B. The unenjoyableevent display window 524 also can include a UI control 532. The UIcontrol 532 can be selected to view events that were enjoyed by the useror other entity (or interpreted to have not been enjoyed). Thus,selection of one of the UI controls 530, 532 can, but does notnecessarily, cause the user device 108 to hide the unenjoyable eventdisplay window 524. Also, selection of the UI control 532 can cause theuser device 108 to present the screen display 500B illustrated anddescribed above with reference to FIG. 5B, though this is notnecessarily the case. Because additional or alternative controls can beincluded in the screen display 500C, it should be understood that theexample embodiment shown in FIG. 5C is illustrative and therefore shouldnot be construed as being limiting in any way.

Referring now to FIG. 5D, a UI diagram showing additional aspects ofsome of the concepts and technologies disclosed herein for providingand/or using an affinity service 106 and/or the affinity application 112is described in detail. In particular, FIG. 5D shows an illustrativescreen display 500D. According to various embodiments, the user device108 can generate the screen display 500D and/or other screen displays inconjunction with and/or based upon interactions with the affinityservice 106 and/or the affinity application 112 described herein (e.g.,via rendering data provided by the affinity service 106 and/or theaffinity application 112, or the like). In the illustrated embodiment,the screen display 500D can be presented, for example, in response todetecting an event and determining, based upon a setting or explicitrequest, that a social networking update should be generated based uponthe event (and/or affinity data 126 associated with the event). Becausethe screen display 500D can be presented at additional and/oralternative times, it should be appreciated that this example isillustrative and therefore should not be construed as being limiting inany way. Also, it should be understood that the UI diagram illustratedin FIG. 5D is illustrative of one contemplated example of the UIs thatcan be generated and/or displayed in accordance with the concepts andtechnologies disclosed herein, and therefore should not be construed asbeing limited in any way.

The screen display 500D can include a social networking status updatewindow 534. It should be understood that the social networking statusupdate window 534 shown in FIG. 5D is one contemplated embodiment of adisplay that can be used to generate a social networking update. Assuch, the illustrated embodiment should not be construed as beinglimiting in any way. As shown in FIG. 5D, the social networking statusupdate window 534 can provide an indication 536 that the socialnetworking update is being generated based upon a detected event and/oraffinity data 126 associated with the event. The social networkingstatus update window 534 also can include a status update window 538.

The status update window 538 can include a status text field 540. Thestatus text field 540 can be pre-populated in some embodiments withaffinity data 126 and/or collected data 118 that can be used to generatethe affinities 120 and/or associated affinity data 126. Thus, the statustext field 540 shown in FIG. 5D can include information describing anevent (e.g., a meeting to talk about a charitable cause), one or morepeople associated with the event (e.g., Eustice Jackson), and moodinformation such as, for example, an indication that the user or otherentity is “calm.” Other moods can be displayed as illustrated anddescribed herein. Other types of affinity data 126 and/or collected data118 can be displayed as well, for example, location information, weatherinformation, music being listened to, food or drink being consumed, aplace of business at which the user or other entity is located, atransaction occurring, or the like. It can be appreciated that a user orother entity can modify the text and/or tags in the status text field540 to thereby modify the status update. Because various types ofinformation that can be collected and/or displayed (e.g., the affinitydata 126 and the collected data 118) have been illustrated and describedherein, only some examples are shown in FIG. 5D. It therefore should beunderstood that the illustrated status text field 540 and thepre-populated information shown therein are illustrative and should notbe construed as being limiting in any way.

The social networking status update window 534 also can include a UIcontrol 542. The UI control 542 can be selected to cause the user device108 to submit the status update to an associated social networkingservice or the like. The social networking status update window 534 alsocan include a UI control 544. The UI control 544 can be selected to editthe status update. Thus, while the text of the status update may beedited via the status text field 540, selection of the UI control 544can cause the user device 108 to display additional editing capabilitiessuch as adding or removing people to “tag” them, adding or removing themood information, adding or removing geographic location information,adding or removing references, combinations thereof, or the like. Thesocial networking status update window 534 also can include a UI control546. The UI control 546 can be selected to cause the user device 108 tocancel the status update. It therefore can be appreciated that selectionof one of the UI controls 542, 544, 546 can, but does not necessarily,cause the user device 108 to hide the social networking status updatewindow 534. Because additional or alternative controls can be includedin the screen display 500D, it should be understood that the exampleembodiment shown in FIG. 5D is illustrative and therefore should not beconstrued as being limiting in any way.

Referring now to FIG. 5E, a UI diagram showing additional aspects ofsome of the concepts and technologies disclosed herein for providingand/or using an affinity service 106 and/or the affinity application 112is described in detail. In particular, FIG. 5E shows an illustrativescreen display 500E. According to some embodiments of the concepts andtechnologies described herein, the screen display 500E can be generatedby a device such as the user device 108 via interactions with theaffinity service 106 and/or the affinity application 112. In particular,according to various embodiments, the user device 108 can generate thescreen display 500E and/or other screen displays in conjunction withand/or based upon interactions with the affinity application 112described herein, which can be configured to render the screen display500E using data generated at the user device 108 and/or using dataprovided by the affinity service 106. It should be appreciated that theUI diagram illustrated in FIG. 5E is illustrative of one contemplatedexample of the UIs that can be generated and/or displayed in accordancewith the concepts and technologies disclosed herein, and thereforeshould not be construed as being limited in any way.

According to various embodiments, the screen display 500E can bepresented, for example, when affinity data 126 is received by the userdevice 108 (e.g., prompted by detected events at the user device 108).Because the screen display 500E illustrated in FIG. 5E can be displayedat additional and/or alternative times, it should be understood thatthese examples are illustrative and therefore should not be construed asbeing limiting in any way. The screen display 500E can include an alertscreen 548. The alert screen 548 can be configured to provide theaffinity data 126 illustrated and described herein to a user or otherentity. In some embodiments, the alert screen 548 can be presented inresponse to detecting an event or condition at the user device 108 (orother device associated with the user or other entity). The alert screen548 can include various types of data and/or information that can beincluded in the affinity data 126.

As illustrated and described herein, the alert screen 548 can provide anindication 550. The indication 550 can explain that some event orcondition information has prompted generation of the alert screen 548.In the illustrated embodiment, the indication 550 can indicate thatmusic by a particular artist has been detected at or proximate to anenvironment 116 associated with the user device 108 (or other device).The indication 550 also can provide mood information (or other affinitydata 126). In the illustrated embodiment, the indication 550 indicatesthat music by a particular artist has been detected and that the user'sor other entity's mood tends to be negatively affected by hearing thismusic (based on the affinity data 126). The indication 550 also includesa suggestion in the illustrated embodiment, though this suggestion isnot necessarily included in all embodiments of the screen display 500E.The suggestion can suggest to the user or other entity how a mood can beimproved, in this case by avoiding listing to the music detected. Thissuggestion can also be based upon the affinity data 126. It should beunderstood that this example is illustrative and therefore should not beconstrued as being limiting in any way.

The alert screen 548 also can include a UI control 552 to dismiss thealert screen 548. Thus, for example, the user or other entity can selectthe UI control 552 to close the alert screen 548 when the desiredinformation has been obtained via the alert screen 548, when the user orother entity wishes to close the alert screen 548 for other reasons,and/or at other times at which the UI control 552 is selected. The alertscreen 548 also can include a UI control 554 for obtaining moreinformation relating to the indication 550 and/or the suggestion.Selection of the UI control 554 can cause the user device 108 to presentadditional and/or alternative affinity information that relates to theevent. Thus, selection of the UI control 554 can cause the user device108 to obtain additional affinity data 126 that can explain theindication 550 and/or the suggestion based upon events, conditions; moodand/or history information associated with a user or other entityassociated with the user device 108 and the location, time, participant,condition, or the like; other information; combinations thereof; or thelike.

The alert screen 548 also can include a prompt 556. The prompt 556 caninform a user or other entity about alerts that may be available and/orhow the affinity service 106 operates. In the illustrated embodiment,the alert screen 548 also includes a UI control 558 to access settingsassociated with the affinity service 106 and/or the affinity application112. Thus, selection of the UI control 558 can cause the user device 108to present settings for generating alerts, tracking moods, detectingevents, combinations thereof, or the like. It can be appreciated thatselection of the UI control 558 also can cause the user device 108 tohide the alert screen 548, though this is not necessarily the case.Because additional or alternative controls can be included in the alertscreen 548, it should be understood that the example embodiment shown inFIG. 5E is illustrative and therefore should not be construed as beinglimiting in any way.

Referring now to FIG. 5F, a UI diagram showing additional aspects ofsome of the concepts and technologies disclosed herein for providingand/or using an affinity service 106 and/or the affinity application 112is described in detail. In particular, FIG. 5F shows an illustrativescreen display 500F. According to some embodiments of the concepts andtechnologies described herein, the screen display 500F can be generatedby a device such as the user device 108 via interactions with theaffinity service 106 and/or the affinity application 112. In particular,according to various embodiments, the user device 108 can generate thescreen display 500F and/or other screen displays in conjunction withand/or based upon creating a calendar event. The user device 108 (and/orthe affinity application 112 executed thereby) can be configured todetect creation of the calendar event and obtain affinity data 126 thatrelates to the calendar event (or some aspect thereof). The user device108 can render the screen display 500F using data generated at the userdevice 108 and/or using data provided by the affinity service 106. Itshould be appreciated that the UI diagram illustrated in FIG. 5F isillustrative of one contemplated example of the UIs that can begenerated and/or displayed in accordance with the concepts andtechnologies disclosed herein, and therefore should not be construed asbeing limited in any way.

According to various embodiments, the screen display 500F can bepresented, for example, when affinity data 126 is received by the userdevice 108 (e.g., prompted by creation of a calendar event at or inassociation with the user device 108). Because the screen display 500Fillustrated in FIG. 5F can be displayed at additional and/or alternativetimes, it should be understood that these examples are illustrative andtherefore should not be construed as being limiting in any way. Thescreen display 500F is illustrated as including a create event screen560. The create event screen 560 can be configured to enable creation ofa calendar event. Because the creation of calendar events generally isunderstood, some of the illustrated fields and/or controls will not befurther described herein.

As illustrated and described herein, the create event screen 560 caninclude a field 562 for specifying invitees or participants of thecalendar event. As shown in FIG. 5F, one invitee or participant (inaddition to the user or other entity) has been specified. The affinityapplication 112 can, in response to detecting creation of the calendarevent, obtain affinity data 126 that relates to any aspect of the event(e.g., location, time, date, title, participants, etc.). In theillustrated embodiment, the affinity application 112 can detect thespecification of the invitee or participant, and obtain affinity data126 relating to the invitee or participant. It should be understood thatthis example is illustrative and therefore should not be construed asbeing limiting in any way.

The create event screen 560 can include an affinity alert field 564. Theaffinity alert field 564 can be displayed anywhere within the createevent screen 560, as an overlay for the create event screen 560, as awindow within the screen display 500F, and/or elsewhere. In someembodiments, the affinity alert field 564 is displayed proximate to thefield with which the affinity alert is associated (in this case thefield 562 for specifying an invitee). It should be understood that thisexample is illustrative and therefore should not be construed as beinglimiting in any way.

The affinity alert field 564 can explain that some event or conditioninformation has prompted generation of the affinity alert field 564. Inthe illustrated embodiment, the affinity alert field 564 can indicatethat the specified invitee or participant is represented by theaffinities 120 and/or other information that may be included in theaffinity data 126. In the illustrated embodiment, the affinity alertfield 564 indicates that information relating to this invitee orparticipant is available.

According to various embodiments, the affinity alert field 564 can alsoact as a UI control that, when selected, causes the user device 108 topresent affinity information that relates to the invitee or participant.Thus, input that corresponds to selection of the affinity alert field564 can cause the user device 108 to obtain affinity data 126 that canprovide insights into the invitee or participant, as well as how thatinvitee or participant can affect a mood associated with the user orother entity. In some embodiments, selection of the affinity alert field564 can cause the user device 108 to display a screen display or othergraphical elements that can present information that may be similar tothe screen display 500A illustrated and described herein with referenceto FIG. 5A, though that is not necessarily the case. Because additionalor alternative controls can be included in the create event screen 560,it should be understood that the example embodiment shown in FIG. 5F isillustrative and therefore should not be construed as being limiting inany way.

Referring now to FIG. 5G, a UI diagram showing additional aspects ofsome of the concepts and technologies disclosed herein for providingand/or using an affinity service 106 and/or the affinity application 112is described in detail. In particular, FIG. 5G shows an illustrativescreen display 500G. According to some embodiments of the concepts andtechnologies described herein, the screen display 500G can be generatedby a device such as the user device 108 via interactions with theaffinity service 106 and/or the affinity application 112. In particular,according to various embodiments, the user device 108 can generate thescreen display 500G and/or other screen displays in conjunction withand/or based upon defining or creating defined moods.

As mentioned above, a “mood” can be subjective, and as such, theconcepts and technologies described herein can provide for defining“moods” and/or defining criteria for projecting “moods” based uponobjective data, as will be explained in more detail below. Because thescreen display 500G can be presented at additional and/or alternativetimes, it should be understood that the above examples are illustrativeand therefore should not be construed as being limiting in any way. Italso should be appreciated that the UI diagram illustrated in FIG. 5G isillustrative of one contemplated example of the UIs that can begenerated and/or displayed in accordance with the concepts andtechnologies disclosed herein, and therefore should not be construed asbeing limited in any way.

The screen display 500G is illustrated as including a condition displayscreen 566. The condition display screen 566 can be configured todisplay conditions associated with the user or other entity. Thus, theconditions at the environment 116 can be displayed by the conditiondisplay screen 566. It can be appreciated from the description hereinthat the conditions displayed by the condition display screen 566 cancorrespond, in some embodiments, to the collected data 118 illustratedand described herein. It should be understood that this example isillustrative and therefore should not be construed as being limiting inany way.

As illustrated and described herein, the condition display screen 566can include a detected condition portion 568. The detected conditionportion 568 can display any number of detected conditions including, butnot limited to, biometric data (e.g., heart rate, blood pressure, oxygensaturation, detected stress level such as variations in other biometricdata), detected states (e.g., whether the user is stationary, sitting,standing, moving, walking, running, driving, or the like), facialexpressions (which can be collected from an onboard imaging device or anoff-board device 114 such as a camera or the like), an audio level(e.g., a decibel level at or near the environment 116), keyword data(e.g., defining keywords that, if detected at the environment 116, canindicate a mood), proximity information (e.g., people or things at ornear the user or other entity), combinations thereof, or the like. Insome embodiments, these and other conditions can be used to set moodsand/or to define moods, though this is not necessarily the case.

The condition display screen 566 can also include a mood indicationportion 570. The mood indication portion 570 can indicate a currentmood. The mood can be defined via various settings and/or configurations(as will be explained in more detail below with reference to FIG. 5H) asexplained in FIG. 1 with regard to the mood data 130. The moodindication portion 570 also can include a UI control that, whenselected, provides mood settings. An example embodiment of a moodsetting screen that can be displayed in response to detecting selectionof the UI control included in the mood indication portion 570 will beillustrated and described in detail below with reference to FIG. 5H.Because additional or alternative controls can be included in thecondition display screen 566, it should be understood that the exampleembodiment shown in FIG. 5G is illustrative and therefore should not beconstrued as being limiting in any way.

Referring now to FIG. 5H, a UI diagram showing additional aspects ofsome of the concepts and technologies disclosed herein for providingand/or using an affinity service 106 and/or the affinity application 112is described in detail. In particular, FIG. 5H shows an illustrativescreen display 500H. According to some embodiments of the concepts andtechnologies described herein, the screen display 500H can be generatedby a device such as the user device 108 via interactions with theaffinity service 106 and/or the affinity application 112. In particular,according to various embodiments, the user device 108 can generate thescreen display 500H and/or other screen displays in conjunction withand/or based upon defining or creating defined moods.

In the illustrated embodiment, the screen display 500H can be presented,for example, in response to detecting a request to define moods and/orobjective data that will be used to define the moods. For example, thescreen display 500H can be presented in response to detecting aninteraction with the UI control illustrated and described above withreference to the mood indication portion 570 in FIG. 5G, though this isnot necessarily the case. Because the screen display 500H can bepresented at additional and/or alternative times, it should beunderstood that this example is illustrative and therefore should not beconstrued as being limiting in any way. Also, it should be understoodthat the UI diagram illustrated in FIG. 5H is illustrative of onecontemplated example of the UIs that can be generated and/or displayedin accordance with the concepts and technologies disclosed herein, andtherefore should not be construed as being limited in any way.

The screen display 500H is illustrated as including a mood settingsscreen 572. The mood settings screen 572 can be configured to displayvarious settings, conditions, condition ranges, and/or other factorsthat can be used to detect or project a mood in accordance with theconcepts and technologies described herein. As such, it can beappreciated that the mood settings screen 572 can be used to generateand/or modify the mood data 130, though this is not necessarily thecase.

As shown in FIG. 5H, a first mood title 574A can indicate and/oridentify a defined mood for which settings and/or conditions in thefirst condition definition portion 576A are defined. Thus, in thecontext of FIG. 5H, the settings and/or conditions in the firstcondition definition portion 576A can define a “calm” mood. Similarly,settings and/or conditions in the second condition definition portion576B can define a “normal” mood as defined in the second mood title574B. It should be understood that these examples are illustrative andtherefore should not be construed as being limiting in any way.

As illustrated and described herein, a diverse set of conditions,condition ranges, and the like can be understood to define a moodassociated with a user or other entity. Not all of these conditions,condition ranges, or the like are illustrated in FIG. 511. Thus, whilethe mood of a particular user or other entity may be affected bygeographic location, date, time of day, places of business, music, foodor drink being consumed, presence or absence of certain individuals orthings; these and other conditions illustrated and described herein arenot shown in FIG. 5H for simplicity. Clearly, however, these and otheraspects of the concepts and technologies described herein can beincluded in various embodiments of the screen display 500H.

As illustrated and described herein, a user or other entity can defineone or more ranges associated with biometric data (e.g., pulse rate,oxygen saturation, stress levels, blood pressures) and/or states can bedefined. According to various embodiments of the concepts andtechnologies described herein, a range may specify one, both, or neitherof a minimum and maximum. In the illustrated embodiment, for example, acalm mood can be defined (at least in part) by having less than amaximum heart rate of 70 beats per minute, having an oxygen saturationof 90% or higher, having a blood pressure of 120/90 or lower, or thelike. It should be understood that this example is illustrative andtherefore should not be construed as being limiting in any way. Theranges illustrated in FIG. 5H can be defined by the user or otherentity.

According to various embodiments of the concepts and technologiesdescribed herein, the user or other entity can use the screen display500G illustrated and described with reference to FIG. 5G to determinethese ranges. In some other embodiments, the affinity service 106 and/orthe affinity application 112 can be configured to periodically pollvarious sensors (e.g., the sensors 110 and/or the off-board devices 114)to collect these and other data, and ask a user or other entity for amood at that time. These and other types of information can be stored asthe mood data 130 illustrated and described herein. Because the rangescan be defined in additional and/or alternative manners, it should beunderstood that these examples are illustrative and therefore should notbe construed as being limiting in any way.

At any rate, by defining various conditions and an associated mood, theaffinity service 106 and/or the affinity application 112 can beconfigured to determine or project, based upon the collected data 118 atany given time, a mood associated with the user or other entity. Thus,when an event is detected and/or at other times, the affinity service106 and/or the affinity application 112 can obtain collected data 118and determine, based upon the collected data 118 and various moodindications stored as part of the affinities 120, a mood or projectedmood associated with the user or other entity. It should be understoodthat this example is illustrative and therefore should not be construedas being limiting in any way.

Although discussed above in detail in various places, it should be notedthat various embodiments of the concepts and technologies describedherein can be used to enable aggregation of affinities 120 by any typeand/or category of information included in (or associated with) theaffinities 120. Thus, various embodiments of the concepts andtechnologies described herein can enable categorization and storage ofthe affinities 120 based upon events, types of events, categories ofevents, conditions, types of conditions, categories of conditions,moods, locations, parties, devices, combinations thereof, or the like.Thus, as explained above, the affinities 120 can be catalogued, stored,and/or searched based upon any information included in and/or associatedwith the affinities 120. It should be understood that this example isillustrative and therefore should not be construed as being limiting inany way.

Time information can be a condition and/or may be used to interpretconditions. For example, a time duration at a particular location,involved in a particular transaction, in the company of a particularperson, etc. may be detected. If the time duration is less than adefined threshold, the condition (with which the time duration isassociated) can be determined not to have an impact on the mood. If thetime duration exceeds the specified threshold, the condition can bedetermined to have an impact on the mood. In some embodiments, the timethresholds may be configured to only apply to some conditions as someconditions may immediately impact mood (e.g., certain activities,certain people, etc.). According to various embodiments, the thresholdcan be defined as thirty seconds, one minute, five minutes, ten minutes,or other time thresholds.

Turning now to FIG. 6, additional details of the network 104 areillustrated, according to an illustrative embodiment. The network 104includes a cellular network 602, a packet data network 604, for example,the Internet, and a circuit switched network 606, for example, apublicly switched telephone network (“PSTN”). The cellular network 602includes various components such as, but not limited to, basetransceiver stations (“BTSs”), Node-B's or e-Node-B's, base stationcontrollers (“BSCs”), radio network controllers (“RNCs”), mobileswitching centers (“MSCs”), mobile management entities (“MMEs”), shortmessage service centers (“SMSCs”), multimedia messaging service centers(“MMSCs”), home location registers (“HLRs”), home subscriber servers(“HSSs”), visitor location registers (“VLRs”), charging platforms,billing platforms, voicemail platforms, GPRS core network components,location service nodes, an IP Multimedia Subsystem (“IMS”), and thelike. The cellular network 602 also includes radios and nodes forreceiving and transmitting voice, data, and combinations thereof to andfrom radio transceivers, networks, the packet data network 604, and thecircuit switched network 606.

A mobile communications device 608, such as, for example, a cellulartelephone, a user equipment, a mobile terminal, a PDA, a laptopcomputer, a handheld computer, and combinations thereof, can beoperatively connected to the cellular network 602. The cellular network602 can be configured as a 2G GSM network and can provide datacommunications via GPRS and/or EDGE. Additionally, or alternatively, thecellular network 602 can be configured as a 3G UMTS network and canprovide data communications via the HSPA protocol family, for example,HSDPA, EUL (also referred to as HSDPA), and HSPA+. The cellular network602 also is compatible with 4G mobile communications standards as wellas evolved and future mobile standards.

The packet data network 604 includes various devices, for example,servers, computers, databases, and other devices in communication withone another, as is generally known. The packet data network 604 devicesare accessible via one or more network links. The servers often storevarious files that are provided to a requesting device such as, forexample, a computer, a terminal, a smartphone, or the like. Typically,the requesting device includes software (a “browser”) for executing aweb page in a format readable by the browser or other software. Otherfiles and/or data may be accessible via “links” in the retrieved files,as is generally known. In some embodiments, the packet data network 604includes or is in communication with the Internet. The circuit switchednetwork 606 includes various hardware and software for providing circuitswitched communications. The circuit switched network 606 may include,or may be, what is often referred to as a plain old telephone system(POTS). The functionality of a circuit switched network 606 or othercircuit-switched network are generally known and will not be describedherein in detail.

The illustrated cellular network 602 is shown in communication with thepacket data network 604 and a circuit switched network 606, though itshould be appreciated that this is not necessarily the case. One or moreInternet-capable devices 610, for example, a PC, a laptop, a portabledevice, or another suitable device, can communicate with one or morecellular networks 602, and devices connected thereto, through the packetdata network 604. It also should be appreciated that theInternet-capable device 610 can communicate with the packet data network604 through the circuit switched network 606, the cellular network 602,and/or via other networks (not illustrated).

As illustrated, a communications device 612, for example, a telephone,facsimile machine, modem, computer, or the like, can be in communicationwith the circuit switched network 606, and therethrough to the packetdata network 604 and/or the cellular network 602. It should beappreciated that the communications device 612 can be anInternet-capable device, and can be substantially similar to theInternet-capable device 610. In the specification, the network 104 isused to refer broadly to any combination of the networks 602, 604, 606.It should be appreciated that substantially all of the functionalitydescribed with reference to the network 104 can be performed by thecellular network 602, the packet data network 604, and/or the circuitswitched network 606, alone or in combination with other networks,network elements, and the like.

FIG. 7 is a block diagram illustrating a computer system 700 configuredto provide the functionality described herein for detecting and usingmood-condition affinities, in accordance with various embodiments of theconcepts and technologies disclosed herein. The computer system 700includes a processing unit 702, a memory 704, one or more user interfacedevices 706, one or more input/output (“I/O”) devices 708, and one ormore network devices 710, each of which is operatively connected to asystem bus 712. The bus 712 enables bi-directional communication betweenthe processing unit 702, the memory 704, the user interface devices 706,the I/O devices 708, and the network devices 710.

The processing unit 702 may be a standard central processor thatperforms arithmetic and logical operations, a more specific purposeprogrammable logic controller (“PLC”), a programmable gate array, orother type of processor known to those skilled in the art and suitablefor controlling the operation of the server computer. As used herein,the word “processor” and/or the phrase “processing unit” when used withregard to any architecture or system can include multiple processors orprocessing units distributed across and/or operating in parallel in asingle machine or in multiple machines. Furthermore, processors and/orprocessing units can be used to support virtual processing environments.Processors and processing units also can include state machines,application-specific integrated circuits (“ASICs”), combinationsthereof, or the like. Because processors and/or processing units aregenerally known, the processors and processing units disclosed hereinwill not be described in further detail herein.

The memory 704 communicates with the processing unit 702 via the systembus 712. In some embodiments, the memory 704 is operatively connected toa memory controller (not shown) that enables communication with theprocessing unit 702 via the system bus 712. The memory 704 includes anoperating system 714 and one or more program modules 716. The operatingsystem 714 can include, but is not limited to, members of the WINDOWS,WINDOWS CE, and/or WINDOWS MOBILE families of operating systems fromMICROSOFT CORPORATION, the LINUX family of operating systems, theSYMBIAN family of operating systems from SYMBIAN LIMITED, the BREWfamily of operating systems from QUALCOMM CORPORATION, the MAC OS, iOS,and/or LEOPARD families of operating systems from APPLE CORPORATION, theFREEBSD family of operating systems, the SOLARIS family of operatingsystems from ORACLE CORPORATION, other operating systems, and the like.

The program modules 716 may include various software and/or programmodules described herein. In some embodiments, for example, the programmodules 716 include the affinity service 106 and the affinityapplication 112. This and/or other programs can be embodied incomputer-readable media containing instructions that, when executed bythe processing unit 702, perform one or more of the methods 200, 300,400 described in detail above with respect to FIGS. 2-4. According toembodiments, the program modules 716 may be embodied in hardware,software, firmware, or any combination thereof. Although not shown inFIG. 7, it should be understood that the memory 704 also can beconfigured to store the collected data 118, affinities 120, the affinitydata 126, mood data 130, and/or other data, if desired.

By way of example, and not limitation, computer-readable media mayinclude any available computer storage media or communication media thatcan be accessed by the computer system 700. Communication media includescomputer-readable instructions, data structures, program modules, orother data in a modulated data signal such as a carrier wave or othertransport mechanism and includes any delivery media. The term “modulateddata signal” means a signal that has one or more of its characteristicschanged or set in a manner as to encode information in the signal. Byway of example, and not limitation, communication media includes wiredmedia such as a wired network or direct-wired connection, and wirelessmedia such as acoustic, RF, infrared and other wireless media.Combinations of the any of the above should also be included within thescope of computer-readable media.

Computer storage media includes volatile and non-volatile, removable andnon-removable media implemented in any method or technology for storageof information such as computer-readable instructions, data structures,program modules, or other data. Computer storage media includes, but isnot limited to, RAM, ROM, Erasable Programmable ROM (“EPROM”),Electrically Erasable Programmable ROM (“EEPROM”), flash memory or othersolid state memory technology, CD-ROM, digital versatile disks (“DVD”),or other optical storage, magnetic cassettes, magnetic tape, magneticdisk storage or other magnetic storage devices, or any other mediumwhich can be used to store the desired information and which can beaccessed by the computer system 700. In the claims, the phrase “computerstorage medium” and variations thereof does not include waves or signalsper se and/or communication media.

The user interface devices 706 may include one or more devices withwhich a user accesses the computer system 700. The user interfacedevices 706 may include, but are not limited to, computers, servers,personal digital assistants, cellular phones, or any suitable computingdevices. The I/O devices 708 enable a user to interface with the programmodules 716. In one embodiment, the I/O devices 708 are operativelyconnected to an I/O controller (not shown) that enables communicationwith the processing unit 702 via the system bus 712. The I/O devices 708may include one or more input devices, such as, but not limited to, akeyboard, a mouse, or an electronic stylus. Further, the I/O devices 708may include one or more output devices, such as, but not limited to, adisplay screen or a printer.

The network devices 710 enable the computer system 700 to communicatewith other networks or remote systems via a network, such as the network104. Examples of the network devices 710 include, but are not limitedto, a modem, a radio frequency (“RF”) or infrared (“IR”) transceiver, atelephonic interface, a bridge, a router, or a network card. The network104 may include a wireless network such as, but not limited to, aWireless Local Area Network (“WLAN”) such as a WI-FI network, a WirelessWide Area Network (“WWAN”), a Wireless Personal Area Network (“WPAN”)such as BLUETOOTH, a Wireless Metropolitan Area Network (“WMAN”) such aWiMAX network, or a cellular network. Alternatively, the network 104 maybe a wired network such as, but not limited to, a Wide Area Network(“WAN”) such as the Internet, a Local Area Network (“LAN”) such as theEthernet, a wired Personal Area Network (“PAN”), or a wired MetropolitanArea Network (“MAN”).

Turning now to FIG. 8, an illustrative mobile device 800 and componentsthereof will be described. In some embodiments, the user device 108described above with reference to FIGS. 1-7 can be configured as and/orcan have an architecture similar or identical to the mobile device 800described herein in FIG. 8. It should be understood, however, that theuser device 108 may or may not include the functionality describedherein with reference to FIG. 8. While connections are not shown betweenthe various components illustrated in FIG. 8, it should be understoodthat some, none, or all of the components illustrated in FIG. 8 can beconfigured to interact with one other to carry out various devicefunctions. In some embodiments, the components are arranged so as tocommunicate via one or more busses (not shown). Thus, it should beunderstood that FIG. 8 and the following description are intended toprovide a general understanding of a suitable environment in whichvarious aspects of embodiments can be implemented, and should not beconstrued as being limiting in any way.

As illustrated in FIG. 8, the mobile device 800 can include a display802 for displaying data. According to various embodiments, the display802 can be configured to display various graphical user interface(“GUI”) elements for creating mood definitions, viewing current moodinformation, viewing affinities 120, viewing alerts relating toaffinities 120, text, images, video, virtual keypads and/or keyboards,messaging data, notification messages, metadata, internet content,device status, time, date, calendar data, device preferences, map andlocation data, combinations thereof, and/or the like. The mobile device800 also can include a processor 804 and a memory or other data storagedevice (“memory”) 806. The processor 804 can be configured to processdata and/or can execute computer-executable instructions stored in thememory 806. The computer-executable instructions executed by theprocessor 804 can include, for example, an operating system 808, one ormore applications 810 such as the affinity application 112, othercomputer-executable instructions stored in a memory 806, or the like. Insome embodiments, the applications 810 also can include a UI application(not illustrated in FIG. 8).

The UI application can interface with the operating system 808 tofacilitate user interaction with functionality and/or data stored at themobile device 800 and/or stored elsewhere. In some embodiments, theoperating system 808 can include a member of the SYMBIAN OS family ofoperating systems from SYMBIAN LIMITED, a member of the WINDOWS MOBILEOS and/or WINDOWS PHONE OS families of operating systems from MICROSOFTCORPORATION, a member of the PALM WEBOS family of operating systems fromHEWLETT PACKARD CORPORATION, a member of the BLACKBERRY OS family ofoperating systems from RESEARCH IN MOTION LIMITED, a member of the IOSfamily of operating systems from APPLE INC., a member of the ANDROID OSfamily of operating systems from GOOGLE INC., and/or other operatingsystems. These operating systems are merely illustrative of somecontemplated operating systems that may be used in accordance withvarious embodiments of the concepts and technologies described hereinand therefore should not be construed as being limiting in any way.

The UI application can be executed by the processor 804 to aid a user inentering content, defining moods, viewing mood definitions, viewingalerts generated by the affinity service 106, viewing and/or editingsocial networking updates, configuring settings, manipulating addressbook content and/or settings, multimode interaction, interacting withother applications 810, and otherwise facilitating user interaction withthe operating system 808, the applications 810, and/or other types orinstances of data 812 that can be stored at the mobile device 800. Thedata 812 can include, for example, the affinity application 112 and/orother applications or program modules. According to various embodiments,the data 812 can include, for example, presence applications, visualvoice mail applications, messaging applications, text-to-speech andspeech-to-text applications, add-ons, plug-ins, email applications,music applications, video applications, camera applications,location-based service applications, power conservation applications,game applications, productivity applications, entertainmentapplications, enterprise applications, combinations thereof, and thelike. The applications 810, the data 812, and/or portions thereof can bestored in the memory 806 and/or in a firmware 814, and can be executedby the processor 804. The firmware 814 also can store code for executionduring device power up and power down operations. It can be appreciatedthat the firmware 814 can be stored in a volatile or non-volatile datastorage device including, but not limited to, the memory 806 and/or aportion thereof.

The mobile device 800 also can include an input/output (“I/O”) interface816. The I/O interface 816 can be configured to support the input/outputof data such as location information, the collected data 118, affinities120, the affinity data 126, mood data 130, user information,organization information, presence status information, user IDs,passwords, and application initiation (start-up) requests. In someembodiments, the I/O interface 816 can include a hardwire connectionsuch as a universal serial bus (“USB”) port, a mini-USB port, amicro-USB port, an audio jack, a PS2 port, an IEEE 1394 (“FIREWIRE”)port, a serial port, a parallel port, an Ethernet (RJ45) port, an RJ11port, a proprietary port, combinations thereof, or the like. In someembodiments, the mobile device 800 can be configured to synchronize withanother device to transfer content to and/or from the mobile device 800.In some embodiments, the mobile device 800 can be configured to receiveupdates to one or more of the applications 810 via the I/O interface816, though this is not necessarily the case. In some embodiments, theI/O interface 816 accepts I/O devices such as keyboards, keypads, mice,interface tethers, printers, plotters, external storage,touch/multi-touch screens, touch pads, trackballs, joysticks,microphones, remote control devices, displays, projectors, medicalequipment (e.g., stethoscopes, heart monitors, and other health metricmonitors), modems, routers, external power sources, docking stations,combinations thereof, and the like. It should be appreciated that theI/O interface 816 may be used for communications between the mobiledevice 800 and a network device or local device.

The mobile device 800 also can include a communications component 818.The communications component 818 can be configured to interface with theprocessor 804 to facilitate wired and/or wireless communications withone or more networks such as the network 104 described herein. In someembodiments, other networks include networks that utilize non-cellularwireless technologies such as WI-FI or WIMAX. In some embodiments, thecommunications component 818 includes a multimode communicationssubsystem for facilitating communications via the cellular network andone or more other networks.

The communications component 818, in some embodiments, includes one ormore transceivers. The one or more transceivers, if included, can beconfigured to communicate over the same and/or different wirelesstechnology standards with respect to one another. For example, in someembodiments one or more of the transceivers of the communicationscomponent 818 may be configured to communicate using GSM, CDMAONE,CDMA2000, LTE, and various other 2G, 2.5G, 3G, 4G, and greatergeneration technology standards. Moreover, the communications component818 may facilitate communications over various channel access methods(which may or may not be used by the aforementioned standards)including, but not limited to, TDMA, FDMA, W-CDMA, OFDM, SDMA, and thelike.

In addition, the communications component 818 may facilitate datacommunications using GPRS, EDGE, the HSPA protocol family includingHSDPA, EUL or otherwise termed HSDPA, HSPA+, and various other currentand future wireless data access standards. In the illustratedembodiment, the communications component 818 can include a firsttransceiver (“TxRx”) 820A that can operate in a first communicationsmode (e.g., GSM). The communications component 818 also can include anN^(th) transceiver (“TxRx”) 820N that can operate in a secondcommunications mode relative to the first transceiver 820A (e.g., UMTS).While two transceivers 820A-N (hereinafter collectively and/orgenerically referred to as “transceivers 820”) are shown in FIG. 8, itshould be appreciated that less than two, two, and/or more than twotransceivers 820 can be included in the communications component 818.

The communications component 818 also can include an alternativetransceiver (“Alt TxRx”) 822 for supporting other types and/or standardsof communications. According to various contemplated embodiments, thealternative transceiver 822 can communicate using various communicationstechnologies such as, for example, WI-FI, WIMAX, BLUETOOTH, infrared,infrared data association (“IRDA”), near field communications (“NFC”),other RF technologies, combinations thereof, and the like. In someembodiments, the communications component 818 also can facilitatereception from terrestrial radio networks, digital satellite radionetworks, internet-based radio service networks, combinations thereof,and the like. The communications component 818 can process data from anetwork such as the Internet, an intranet, a broadband network, a WI-FIhotspot, an Internet service provider (“ISP”), a digital subscriber line(“DSL”) provider, a broadband provider, combinations thereof, or thelike.

The mobile device 800 also can include one or more sensors 824. Thesensors 824 can include temperature sensors, light sensors, air qualitysensors, movement sensors, orientation sensors, noise sensors, proximitysensors, or the like. As such, it should be understood that the sensors824 can include, but are not limited to, accelerometers, magnetometers,gyroscopes, infrared sensors, noise sensors, microphones, combinationsthereof, or the like. Additionally, audio capabilities for the mobiledevice 800 may be provided by an audio I/O component 826. The audio I/Ocomponent 826 of the mobile device 800 can include one or more speakersfor the output of audio signals, one or more microphones for thecollection and/or input of audio signals, and/or other audio inputand/or output devices.

The illustrated mobile device 800 also can include a subscriber identitymodule (“SIM”) system 828. The SIM system 828 can include a universalSIM (“USIM”), a universal integrated circuit card (“UICC”) and/or otheridentity devices. The SIM system 828 can include and/or can be connectedto or inserted into an interface such as a slot interface 830. In someembodiments, the slot interface 830 can be configured to acceptinsertion of other identity cards or modules for accessing various typesof networks. Additionally, or alternatively, the slot interface 830 canbe configured to accept multiple subscriber identity cards. Becauseother devices and/or modules for identifying users and/or the mobiledevice 800 are contemplated, it should be understood that theseembodiments are illustrative, and should not be construed as beinglimiting in any way.

The mobile device 800 also can include an image capture and processingsystem 832 (“image system”). The image system 832 can be configured tocapture or otherwise obtain photos, videos, and/or other visualinformation. As such, the image system 832 can include cameras, lenses,charge-coupled devices (“CCDs”), combinations thereof, or the like. Themobile device 800 may also include a video system 834. The video system834 can be configured to capture, process, record, modify, and/or storevideo content. Photos and videos obtained using the image system 832 andthe video system 834, respectively, may be added as message content toan MMS message, email message, and sent to another mobile device. Thevideo and/or photo content also can be shared with other devices viavarious types of data transfers via wired and/or wireless communicationdevices as described herein.

The mobile device 800 also can include one or more location components836. The location components 836 can be configured to send and/orreceive signals to determine a geographic location of the mobile device800. According to various embodiments, the location components 836 cansend and/or receive signals from global positioning system (“GPS”)devices, assisted-GPS (“A-GPS”) devices, WI-FI/WIMAX and/or cellularnetwork triangulation data, combinations thereof, and the like. Thelocation component 836 also can be configured to communicate with thecommunications component 818 to retrieve triangulation data fordetermining a location of the mobile device 800. In some embodiments,the location component 836 can interface with cellular network nodes,telephone lines, satellites, location transmitters and/or beacons,wireless network transmitters and receivers, combinations thereof, andthe like. In some embodiments, the location component 836 can includeand/or can communicate with one or more of the sensors 824 such as acompass, an accelerometer, and/or a gyroscope to determine theorientation of the mobile device 800. Using the location component 836,the mobile device 800 can generate and/or receive data to identify itsgeographic location, or to transmit data used by other devices todetermine the location of the mobile device 800. The location component836 may include multiple components for determining the location and/ororientation of the mobile device 800.

The illustrated mobile device 800 also can include a power source 838.The power source 838 can include one or more batteries, power supplies,power cells, and/or other power subsystems including alternating current(“AC”) and/or direct current (“DC”) power devices. The power source 838also can interface with an external power system or charging equipmentvia a power I/O component 840. Because the mobile device 800 can includeadditional and/or alternative components, the above embodiment should beunderstood as being illustrative of one possible operating environmentfor various embodiments of the concepts and technologies describedherein. The described embodiment of the mobile device 800 isillustrative, and should not be construed as being limiting in any way.

Based on the foregoing, it should be appreciated that systems andmethods for detecting and using mood-condition affinities have beendisclosed herein. Although the subject matter presented herein has beendescribed in language specific to computer structural features,methodological and transformative acts, specific computing machinery,and computer-readable media, it is to be understood that the conceptsand technologies disclosed herein are not necessarily limited to thespecific features, acts, or media described herein. Rather, the specificfeatures, acts and mediums are disclosed as example forms ofimplementing the concepts and technologies disclosed herein.

The subject matter described above is provided by way of illustrationonly and should not be construed as limiting. Various modifications andchanges may be made to the subject matter described herein withoutfollowing the example embodiments and applications illustrated anddescribed, and without departing from the true spirit and scope of theembodiments of the concepts and technologies disclosed herein.

We claim:
 1. A system comprising: a processor; and a memory that storescomputer-executable instructions that, when executed by the processor,cause the processor to perform operations comprising obtaining moodinformation associated with a user of a user device, the moodinformation comprising biometric information, defining, based on themood information, a plurality of moods for the user, obtaining, from theuser device, collected data comprising sensor readings collected by theuser device, wherein the sensor readings comprise a first sensor readingthat relates to an environment of the user device, and a second sensorreading that relates to the user, wherein the second sensor readingcomprises audio captured by a microphone of the user device,determining, based on the first sensor reading, a condition in theenvironment of the user device, determining, based on the second sensorreading, a mood associated with the user, wherein determining the moodcomprises detecting, in the audio captured by the microphone, keywordsin spoken words represented by the audio and determining, based on thekeywords, the mood, generating an affinity that defines a relationshipbetween the condition and the mood, and storing the affinity at a datastorage device.
 2. The system of claim 1, wherein thecomputer-executable instructions, when executed by the processor, causethe processor to perform operations further comprising: detecting anevent occurring at the user device, the event comprising a change instate associated with the user; and requesting the collected data inresponse to detecting the event.
 3. The system of claim 1, furthercomprising sensors located at the user device and off-board devices incommunication with the user device, wherein the off-board devicescomprise a camera, and wherein the sensors comprise biometric sensors.4. The system of claim 1, wherein the second sensor reading comprisesbiometric data, and wherein determining the mood comprises identifyingone of the plurality of moods that comprises biometric information thatrelates to the biometric data.
 5. The system of claim 1, wherein thecomputer-executable instructions, when executed by the processor, causethe processor to perform operations further comprising: receiving, froma requestor, a request for affinity data; determining a furthercondition that is associated with the requestor; identifying a furtheraffinity associated with the further condition; and providing theaffinity data to a recipient, the affinity data being based upon thefurther affinity.
 6. The system of claim 1, wherein thecomputer-executable instructions, when executed by the processor, causethe processor to perform operations further comprising: generating asocial networking status update; and providing the social networkingstatus update to a device that hosts a social networking service,wherein the social networking status update relates to the user andindicates mood.
 7. The system of claim 5, wherein providing the affinitydata to the recipient comprises providing an alert to the recipient,wherein the alert relates to an event associated with the requestor, andwherein the alert indicates a predicted mood of the user based on aprojected condition.
 8. The system of claim 1, wherein the first sensorreading comprises the audio captured by the microphone, and whereindetermining the condition comprises recognizing, in the audio capturedby the microphone, music in the environment.
 9. A computer storagemedium having computer-executable instructions stored thereon that, whenexecuted by a processor, cause the processor to perform operationscomprising: obtaining mood information associated with a user of a userdevice, the mood information comprising biometric information; defining,based on the mood information, a plurality of moods for the user;obtaining, from the user device, collected data comprising sensorreadings collected by the user device, wherein the sensor readingscomprise a first sensor reading that relates to an environment of theuser device, and a second sensor reading that relates to the user,wherein the second sensor reading comprises audio captured by amicrophone of the user device; determining, based on the first sensorreading, a condition in the environment of the user device; determining,based on the second sensor reading, a mood associated with the user,wherein determining the mood comprises detecting, in the audio capturedby the microphone, keywords in spoken words represented by the audio anddetermining, based on the keywords, the mood; generating an affinitythat defines a relationship between the condition and the mood; andstoring the affinity at a data storage device.
 10. The computer storagemedium of claim 9, wherein the second sensor reading comprises biometricdata, and wherein determining the mood comprises identifying one of theplurality of moods that comprises biometric information that relates tothe biometric data.
 11. The computer storage medium of claim 9, whereinthe computer-executable instructions, when executed by the processor,cause the processor to perform operations further comprising: receiving,from a requestor, a request for affinity data; determining a furthercondition that is associated with the requestor; identifying a furtheraffinity associated with the further condition; and providing theaffinity data to a recipient, the affinity data being based upon thefurther affinity.
 12. The computer storage medium of claim 11, whereinreceiving the request for the affinity data comprises: obtaining furthercollected data from the requestor; determining the further condition;and determining, by the processor and based on the further condition,that the affinity data should be provided to the recipient.
 13. A methodcomprising: obtaining, at a processor that executes an affinity service,mood information associated with a user of a user device, the moodinformation comprising biometric information; defining, by the processorand based on the mood information, a plurality of moods for the user;obtaining collected data comprising sensor readings collected by theuser device, wherein the sensor readings comprise a first sensor readingthat relates to an environment of the user device, and a second sensorreading that relates to the user, wherein the second sensor readingcomprises audio captured by a microphone of the user device;determining, by the processor and based on the first sensor reading, acondition in the environment of the user device; determining, by theprocessor and based on the second sensor reading, mood associated withthe user, wherein determining the mood comprises detecting, in the audiocaptured by the microphone, keywords in spoken words represented by theaudio and determining, based on the keywords, the mood; generating, bythe processor, an affinity that defines a relationship between thecondition and the mood; and storing, by the processor, the affinity at adata storage device.
 14. The method of claim 13, wherein the secondsensor reading comprises biometric data, and wherein determining themood comprises identifying one of the plurality of moods that comprisesbiometric information that relates to the biometric data.
 15. The methodof claim 13, further comprising: receiving, by the processor and from arequestor, a request for affinity data; determining, by the processor, afurther condition that is associated with the requestor; identifying, bythe processor, a further affinity associated with the further condition;and providing, by the processor, the affinity data to a recipient, theaffinity data being based upon the further affinity.
 16. The method ofclaim 13, further comprising: generating a social networking statusupdate; and providing the social networking status update to a devicethat hosts a social networking service, wherein the social networkingstatus update relates to the user and indicates mood.
 17. The method ofclaim 15, wherein providing the affinity data to the recipient comprisesproviding an alert to the recipient, wherein the alert relates to anevent associated with the requestor and wherein the alert indicates apredicted mood of the user based on a projected condition.
 18. Themethod of claim 15, wherein receiving the request for the affinity datacomprises: obtaining, by the processor, further collected data from therequestor; determining, by the processor, the further condition; anddetermining, by the processor and based on the further condition, thataffinity data should be provided to the recipient.